cloudy cloudy

Author Topic: Corrupt clientraw files  (Read 2994 times)

0 Members and 1 Guest are viewing this topic.

Offline niko

  • syzygy
  • Global Moderator
  • Posts: 26,969
  • Crystal Ball broken! Please post the URL.
  • Northern California, U.S.A.
  • OS/Browser:
  • Win 7/Srvr 2008R2
  • Chrome 56.0.2924.87
Re: Corrupt clientraw files
« Reply #30 on: April 05, 2017, 02:34:07 PM »
So Wim is correct "When not using the URL location in the wdlconfig.xml, WD-Live looks for the file in the current folder and will not use more a more complicated file-access using http://"  :D 

Offline wvdkuil

  • Wim van der Kuil
  • Posts: 759
  • Amsterdam / Netherlands
  • OS/Browser:
  • Mac OS X 10.12.3
  • Chrome 57.0.2987.98
    • My private weatherstation
Re: Corrupt clientraw files
« Reply #31 on: April 05, 2017, 02:38:06 PM »

If I do like Wim says (over), i.e. remove the pointers to clientraw files in wdlconfig (in wddata directory), the WDL actually starts and works from "inside"; starting it from index.html in the wddata directory. Strangely it seems that if I restore the wdlconfig (with the pointers), and then try to start, WDL returns same error message.

If the pointers (= URL http:// . . . . ) are removed from the  xml, WDL will read the files as a local file from the wddata folde
=> there should be no error message as a 404 is not used in that case and if the file is present WDL will process it.

With the pointers (= URL http:// . . . . ) in the  xml, WDL will read the files as an external file and the 404 error message will occur.
For WDL as for the clientraw parser, that strange 404 error message is certainly NOT a clientraw.txt and WDL will issue its own message.

Does not matter where you startt WDL from, from inside or outside your house.
For IIS => http:// means an external request and with  a .txt file it will generate the error message.

« Last Edit: April 05, 2017, 02:40:53 PM by wvdkuil »
Vantage VUE with a WLIP used for
Vantage VP2 with a USB logger/Meteobridge for