Greg,
I am very sure since port 8443 is blocked by a firewall. That is how I
noticed the problem: the application generates some URLs that are
derived from the URL of the page request and these now contain a port
number and are blocked.
Kind regards,
Silvio
On 11-08-2023 15:27, Greg Wilkins wrote:
Silvio,
The host header should contain the host and port as used by the
client. Thus if the request goes to the default port and is forward
you a different port, the host header should not have the port in it,
or at least only the default port.
Are you sure the client is using the default port and not going direct
you the server?
Can you give us a bit more info:
+ Uri and headers as sent by the client
+ Uri and headers as received by jetty
+ The actual values you get from the various request methods
Cheers
On Fri, Aug 11, 2023, 21:34 Silvio Bierman via jetty-users
<[email protected]> wrote:
Hello all,
I have encountered what I think is a bug in Jetty 12 but I would
like to
check here if that is actually true.
I use port forwarding to forward HTTP requests from port 443 to 8443.
Requests arrive at the default port without an explicit port
number in
the URL so
request.getRequestURL().toString
does not show a port number. But
request.getHeader("Host")
returns the host name including the port number. This makes it
impossible to distinguish requests with explicit ports from requests
without these. Jetty 11 does not show this same behaviour.
Cheers,
Silvio
_______________________________________________
jetty-users mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
