I recently saw this in my website's httpd-error.log, can your pls tell me
what I should check? I really have no clue where to look:
File does not exist: /usr/www/mywebsite.net/://
Looks like something is missing? Site looks oke, visually no quircks to be
seen.
Can you tell me what might cause this? Thanks!
--
Floor
On Nov 2, 2:08 pm, "Floor"
> I recently saw this in my website's httpd-error.log, can your pls tell me
> what I should check? I really have no clue where to look:
>
> File does not exist: /usr/www/mywebsite.net/://
>
> Looks like something is missing? Site looks oke, visually no quircks to be
> seen.
> Can you tell me what might cause this? Thanks!
>
> --
> Floor
Open internet explorer and type
http://www.mywebsite.net/://
into the address bar.
Thats one way - there are others, depending on your apache
configuration.
shimmyshack:
> Open internet explorer and type
> http://www.mywebsite.net/://
> into the address bar.
>
> Thats one way - there are others, depending on your apache
> configuration.
Yes I know; but I want to get rid of it in my httpd-error.log. Does that
implicate that a user requests this URL format or is it a fault somewhere in
my site and if so, how could I solve it...
thanks,
Floor
"Floor"
news:472c5d04$0$226$e4fe514c@news.xs4all.nl...
>> Open internet explorer and type
>> http://www.mywebsite.net/://
>> into the address bar.
>>
>> Thats one way - there are others, depending on your apache
>> configuration.
>
> Yes I know; but I want to get rid of it in my httpd-error.log. Does that
> implicate that a user requests this URL format or is it a fault somewhere
> in my site and if so, how could I solve it...
>
Check the access_log to see the corresponding incoming, unmodified request.
With a bit of luck the referrer will reveal the in-site cause.
Further, you cann't surpress logging of an error, you can correctively
rewrite [the mapping of ]a bogus URL to avoid the error to occure. Be
careful not to trip Google's 'too many links to same content' trap ...
HansH
HansH:
> Check the access_log to see the corresponding incoming, unmodified
> request.
> With a bit of luck the referrer will reveal the in-site cause.
>
> Further, you cann't surpress logging of an error, you can correctively
> rewrite [the mapping of ]a bogus URL to avoid the error to occure. Be
> careful not to trip Google's 'too many links to same content' trap ...
That makes sense to me... I will do as you advised, thanks for your comment.
Floor