GET requests in Medusa web server
Hello all, Why does the Medusa server in Zope not handle GET requests which specify a full URI? For example, if I have a web server running on web.mydomain.com, and I want to get a file called "file.html", doing a GET request of the form GET http://web.mydomain.com/file.html HTTP/1.1 gives me a 404. Doing a GET of the form GET /file.html HTTP/1.1 works fine. If I understand RFC 2068 correctly, a HTTP 1.1 compliant server is expected to handle both cases (5.1.12 of RFC 2068), although HTTP 1.1 clients are not supposed to generate these unless talking to a proxy. In our case, the software which generates the request is a WAP gateway (Ophelia, http://www.3ui.com), and it always assumes it is talking to a proxy server, and requires a code change to change it. I've tested Apache and IIS with this, and they handle both forms. Thanks in advance.
Why does the Medusa server in Zope not handle GET requests which specify a full URI? For example, if I have a web server running on web.mydomain.com, and I want to get a file called "file.html", doing a GET request of the form
GET http://web.mydomain.com/file.html HTTP/1.1
gives me a 404. Doing a GET of the form
GET /file.html HTTP/1.1
works fine. If I understand RFC 2068 correctly, a HTTP 1.1 compliant server is expected to handle both cases (5.1.12 of RFC 2068) ...
Hi Sean - What version of Zope are you seeing this with? I seem to remember fixing something along these lines fairly recently. Is it still the case in Zope 2.2.2? Brian Lloyd brian@digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com
At 10:42 AM 10/23/00 -0400, Brian Lloyd wrote:
Why does the Medusa server in Zope not handle GET requests which specify a full URI? For example, if I have a web server running on web.mydomain.com, and I want to get a file called "file.html", doing a GET request of the form
GET http://web.mydomain.com/file.html HTTP/1.1
gives me a 404. Doing a GET of the form
GET /file.html HTTP/1.1
works fine. If I understand RFC 2068 correctly, a HTTP 1.1 compliant server is expected to handle both cases (5.1.12 of RFC 2068) ...
Hi Sean -
What version of Zope are you seeing this with? I seem to remember fixing something along these lines fairly recently. Is it still the case in Zope 2.2.2?
I am using Zope 2.1.6. regards, Sean http://www.pyxie.org - an Open Source XML Processing library for Python
participants (2)
-
Brian Lloyd -
Sean McGrath