Paul,
Jetty will extract from to a temp web-inf directory to avoid the jar inside
war class loading issues when a war file is not unpacked. It should not
be doing this if the webapp is unpacked. It should definitely not put both
on the classpath.
I think we may have a bug here. We will
Silvio,
Let's get your existing code working but then I'd really like to show
you how you can use jetty-12 handlers to do that expansion for you prior to
any buffering and/or blocking input streams.
cheers
On Tue, 12 Sept 2023 at 03:47, Simone Bordet via jetty-users <
I've done a draft PR to potentially fix this:
https://github.com/eclipse/jetty.project/pull/10479
But we need to actually write a test to confirm the diagnosis first.
On Tue, 5 Sept 2023 at 17:44, Jan Bartel via jetty-users <
jetty-users@eclipse.org> wrote:
> Silvio,
>
>
> This looks like a url
Actually,
I think Uwe's and Silvio's problems are similar but different.
Silvio, you have no forwarded request customizer headers and a real
"demo.jambo.software:8443" as the host header value. This could be a http2
issue in recreating that header.
Uwe's issue is more about the customizer.
So
Silvio,
I'll respond more in Uwe's issue. Please post your details there to help
the triage.
cheers
On Sun, 13 Aug 2023 at 05:19, Uwe Schindler via jetty-users <
jetty-users@eclipse.org> wrote:
> I opened: https://github.com/eclipse/jetty.project/issues/10304
> Am 12.08.2023 um 19:30
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
