| 2:18 pm on Aug 21, 2003 (gmt 0)|
when opening the browser; not having any page to go back to?
Or the back page might have timed out?
| 2:22 pm on Aug 21, 2003 (gmt 0)|
Hmmm... really tempting to say "Rude, or otherwise ignorant posts will be summarily ignored" Hehehe ;)
[added: Oops, I posted before refreshing my browser, so i thought my post would be #2... My first comment (the bit of levity) was not refering to fashezee's post in any way)]
[edited by: ShawnR at 2:34 pm (utc) on Aug. 21, 2003]
| 2:25 pm on Aug 21, 2003 (gmt 0)|
Oops, ShawnR got it first.
Yep, the parsed js should be reflected in the GET. And for pages accessed directly with no history the script simply does not execute and doesn't whow up as an entry in the logs.
| 4:04 pm on Aug 21, 2003 (gmt 0)|
The other option is that somewhere on your site you have:
What UA is associated with this log entry?
| 4:32 pm on Aug 21, 2003 (gmt 0)|
| 5:17 pm on Aug 21, 2003 (gmt 0)|
I never realized that, didn't ever think to test it. I've never seen any except the standard 'back' scripts. Do you happen to know if there are any that take this into account? Or if it's something that just has to be lived with?
| 5:48 pm on Aug 21, 2003 (gmt 0)|
The "/" char. is not an escape; it is treated as a valid file character. Someone was playing around in the address bar and didn't delete the "/" so the browser didn't know it was JS and requested it as a filename. That would be my guess.
| 6:38 pm on Aug 21, 2003 (gmt 0)|
You could use <!--#echo var="REFERER"--> and place it in the "href" section. But if user has disabled referer then you are out of luck. IMO just leave it up to the user and standard browser interface.
"/" char comes naturally with HTTP request, that is the way HTTP works.
GET / - gets the root of the server