Bug 56933

Summary:	not sure it's an appache bug : some browser want to get file/directory replacing mine with a dot
Product:	Apache httpd-2	Reporter:	ch.derenne
Component:	Build	Assignee:	Apache HTTPD Bugs Mailing List <bugs>
Status:	RESOLVED LATER
Severity:	minor	Keywords:	MassUpdate
Priority:	P2
Version:	2.2.23
Target Milestone:	---
Hardware:	PC
OS:	Linux

Description ch.derenne 2014-09-09 08:42:29 UTC

Well: not sure it's an apache bug, so if not, please telle me where I can have information about this :

I've several site that work perfecly,
but in my apache error log, there is a lot of lines that say "not found or unable tot stat" about some of mine site's files but replacing le first car by a dot.
Exemple :
You have 1 index.html file with 1 style.css file, a folder : 'photo' and image.jpg inside.
You have 15000 visitir's by day, nobody seems to have trouble (i've never succeed to repeated this)

Apache error log are full of this :
[Wed Aug 27 08:22:24 2014] [error] [client 213.138.23.68] File does not exist: /var/www/html/.tyle.css, referer: http://xxx.xxx.xxx/
[Wed Aug 27 08:22:24 2014] [error] [client 213.138.23.68] File does not exist: /var/www/html/.hoto/image.jpg, referer: http://xxx.xxx.xxx/
(the first car have been replaced by a dot).

For each of this, I see that the user agent is :
"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB7.2; .NET CLR 1.1.4322; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; WallaIE7)"

For all other user-agent, everything is ok, and I don't know how to get the exactly same useragent configuration to make some tests

So, what is wrong ?

Comment 1 William A. Rowe Jr. 2018-11-07 21:08:09 UTC

Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.