Edouard,
thanks for your warm welcome. I'll honor that later in the "new member area".
Blick,
thanks for taking the time, but I meanwhile was able to identify the problem.
In short, all of the files are in the places they belong. It's the WASD webserver being too smart...
GAUGES.JS calls REALTIMEGAUGESWC.TXT and appends a number to the URL.
http://michelswunderland.de/weather/realtimegaugeswc.txt?_=12345678901234The number appended is the system's time plus a counter - this is nothing but a trick to prevent
the page being cached.
The WASD webserver doesn't allow to pass parameters to files not being procedures or executables.
Moving the .TXT to the cgi-bin directory does help neither - the WASD webserver throws an error
that it can't start the file... it's pretty obvious why :-)
I've put the whole gear onto my VMS machine at home which is running an Apache webserver ...
and there it worked right out of the box... unfortunately, this machine is not running 24*365...
I think it's a configuration matter with the WASD webserver, but I think the owner of the machine
the WASD is runnning on has set this behaviour for an obvious reason - the "?whatever" appendix
to an URL can be used for nasty things...
The only solution to this problem seems to be a modification of GAUGES.JS so that it won't
append the parameter salad to the URL and to somehow prevent the page from being cached.
I think appending the parameter will happen around line 2614 in GAUAGES.JS,
but I'm not able to recognize how it is done...
So the question to the JavaScript experts here is:
What mod do I have to apply to GAUGES.JS so that it won't append the parameter to the URL ?
Regards !
Michel