How do you prevent HttpWatch from interpreting javascript single-line comment as call to a missing resource thus resulting in a 404 error?
+2
A:
Perhaps you should ask the HttpWatch-guys? This has nothing to do with javascript.
KooiInc
2009-02-16 08:34:52
A:
I think it thinks that the //… is intended to be a relative URI just without the scheme.
Gumbo
2009-02-16 09:00:39
+1
A:
HttpWatch doesn't interpret the javascript - it just records the HTTP traffic generated by the browser. Any 404 error that you see is merely being reported by HttpWatch not generated by it.
If you can provide a .hwl file from HttpWatch or a public URL where this occurs we'll have a look to see why the 404 is generated.
You can contact us directly at [email protected].
HttpWatchSupport
2009-02-16 11:38:27
A:
The original poster could be referring to the invalid URL http://:/ appearing in the HttpWatch log. This is a side effect of a commonly used technique in javascript libraries that attempt to emulate a DOMContentLoaded event in IE:
http://blog.httpwatch.com/2007/11/20/error_internet_invalid_url-httpwatch/
HttpWatchSupport
2009-03-06 14:20:20