Duane Wessels wrote:
> I'm just really tired of broken browsers and servers generating
> requests that make it look like a Squid bug. If the browsers are not
> willing to turn an Invalid URL into a valid one, then I am willing to
> do it with Squid given the guidance in RFC 2396.
As I said I am not sure that section (Appendix E, Recommendations for
Delimiting URI in [unclear textual] Context) applies to HTTP. It relates
to spaces introduced by humans or as part automatic formatting.
Also following the recommendation breaks current practise. Close to none
of the URI's seen on squid-users can be expected to work if the spaces
are ignored as the servers expect the spaces (possibly encoded) as part
of the URI. Without the space these URI's take a different meaning,
possibly returning different result (or error).
In other words, if you change the default to ignore spaces then I am
afraid the questions will shift from "why do I get this Squid error" to
"why doesn't this page work properly when I use Squid", and this
question is much harder to answer.
My recommendation is to change the default to allow, OR add a comment to
the error page mentioning that space characters is not acceptable.
/Henrik
Received on Wed Nov 24 1999 - 01:10:40 MST
This archive was generated by hypermail 2.2.0 : Wed Apr 09 2008 - 12:01:56 MDT