Re: general/4911: URLS like "http://www.apache.org/index.html/" should return a NOT FOUND, but don't.

[Marc Evans <ma...@destek.net>]

Thank you for your followup. I am curious, do you consider the
browsers as having a bug in that the images referenced by the URL
that are referenced as reletive links can not be found, apprently
due to how the browser interprets the URL? In other words, the
browsers present different results depending upon if the trailing
slash is included or not.

If you believe that it is a bug, I will try to submit bug reports to
each of the browser creators, if you agree with the assertion.

Thanks - Marc

---- In reference to:

Date: 27 Aug 1999 17:28:03 -0000
Message-ID: <19...@hyperreal.org>
To: apache-bugdb@apache.org, coar@apache.org, marc@xfree86.org
From: coar@apache.org
Subject: Re: general/4911: URLS like "http://www.apache.org/index.html/" should return a NOT FOUND, but don't.

[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: URLS like "http://www.apache.org/index.html/" should return a NOT FOUND, but don't.

Comment-Added-By: coar
Comment-Added-When: Fri Aug 27 10:27:56 PDT 1999
Comment-Added:

No, the current behaviour is exactly correct.  The trailing
slash is part of the PATH_INFO.

Class-Changed-From-To: sw-bug-mistaken
Class-Changed-By: coar
Class-Changed-When: Fri Aug 27 10:27:56 PDT 1999

Re: general/4911: URLS like "http://www.apache.org/index.html/" should return a NOT FOUND, but don't.

[Rodent of Unusual Size <Ke...@Golux.Com>]

Marc Evans wrote:
> 
> Thank you for your followup. I am curious, do you consider the
> browsers as having a bug in that the images referenced by the URL
> that are referenced as reletive links can not be found, apprently
> due to how the browser interprets the URL? In other words, the
> browsers present different results depending upon if the trailing
> slash is included or not.

An interesting point.  But no, I don't think that's a bug -- the
browsers are behaving correctly.  They have no way of knowing where
the path-info begins.

If a resource is capable of accepting path-info, it really should
have the responsibility of correctly coding internal relative
references so they appear as absolute to the client, and avoid
this ambiguity.

Do you have specific cases on the Apache site where this is
done?  Because they should be fixed if so..
-- 
#ken    P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Software Foundation  <http://www.apache.org/>
"Apache Server for Dummies" <http://ASFD.MeepZor.Com/>