https://bz.apache.org/bugzilla/show_bug.cgi?id=65365
Fuwei Chin <fuweic...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |---
--- Comment #2 from Fuwei Chin <fuweic...@gmail.com> ---
As RFC 2116 describes:
> Request-Line = Method SP Request-URI SP HTTP-Version CRLF
> Request-URI = "*" | absoluteURI | abs_path | authority
See https://datatracker.ietf.org/doc/html/rfc2616#section-5.1 and
https://datatracker.ietf.org/doc/html/rfc7230#section-3.1.1
"Custom HTTP methods are already supported", Yes. while I mean the Request-URI.
A forward proxy requires the capability to accept CONNECT request and handle
absoluteURI request.
A CONNECT request uses authority as Request-URI, while authority as Request-URI
is not currently supported by Tomcat, Tomcat rejects CONNECT request with "400
Bad Request" before entering `MyGenericServlet#serice()`. And a
request-to-proxy request uses absoluteURI as Request-URI, which is not fully
supported by Tomcat, since the original absoluteURI cannot be obtained through
Servlet API `HttpServletRequest#getRequestURI()`.
I ask for HTTP Tunneling (Forward Proxy) Support, maybe there are better
approaches.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
