Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 6.1.1
-
Fix Version/s: None
-
Component/s: HTTP
-
Labels:None
-
Number of attachments :
Description
While Jetty does not pretend to be a full-blown proxy server, correct handling of proxy requests is quite desirable. With ProxyServlet Jetty correctly handles HTTP proxy requests. However, HTTPS and CONNECT method fail even though ProxyServlet seems to be equipped to handle them. The problem arises earlier - in Request: it incorrectly parses CONNECT string. Unlike proxied GET of HTTP, CONNECT does not include the protocol for the target server. Browsers send "CONNECT mail.yahoo.com:443" rather than "CONNECT https://mail.yahoo.com". At this point HttpURI's parsing completely breaks down: it interpretes host as scheme, port as path etc.
Issue Links
| This issue duplicates: | ||||
| JETTY-190 | Convert HttpTunnel and HttpMessage to Jetty 6 |
|
|
|
The Jetty 5 proxy Handler does correctly handle CONNECT
I don't think that CONNECT can be well handled within a servlet and the proxyservlet is really just an experiment.
We will soon be doing a Jetty 6 handler that will have full CONNECT capability.
watch this space....