>Theoretically, it shouldn't break anything that uses proper
HTTP/1.0.
>The use of the suffix to determine file type occurs only if it
doesn't
>get a proper HTTP/1.0 response. If it gets a HTTP/1.0 response then
>the code should ignore the suffix.
But it will break HTTP/0.9 which
Consider the entry in a gatewayed database
http://.../amc56.figu.88.04.gif
GIF8756 is the interface module responable for the interface
Sounds contrived but there is a valid server converting valid
So what do we do?
especially gateways which
The only client I think which
Tim
And specifies taht the url is opaque.
where the end gif in fact stands for "Group d'Interfaces
Foncionelles" and is a database partition. The text comming back
is
monitoring of the valve closure pressure release mechanisms.
It is currently
<PRE>
ON
</PRE>
url into valid documet, which
any way they please. We can't say "but not use dots"
at this stage. And we can't enforce that gateways use HTTP1.0
because the ability to make a script gateway trivially is
really neat.
be able to use HTTP 0.9.