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
I opened: https://github.com/eclipse/jetty.project/issues/10304
Am 12.08.2023 um 19:30 schrieb Uwe Schindler via jetty-users:
I have seen the same after upgrading my project to Java 12. The
problem is that all Customizers are not able to correctly set the port
number.
This is a blocker
Hi,
I have seen the same after upgrading my project to Java 12. The problem
is that all Customizers are not able to correctly set the port number.
This is a blocker issue, because it makes it impossible to setup this
common setup:
* NGINX as user facing web server with HTTPS enabled
*
Your best bet will be to reach out to the eclipse webmasters since they're
the ones that have rights to manage the eclipse mailing lists.
https://gitlab.eclipse.org/eclipsefdn/helpdesk
Cheers!
Jesse
On Sat, Aug 12, 2023, 04:49 Someone via jetty-users
wrote:
> Since April this year I'm
Since April this year I'm suddenly getting messages from this list. I was
unsubscribed successfully way back on Jan 4 2022. I've now tried to unsubscribe
myself in two ways:
- sending email to jetty-users-requ...@eclipse.org, but It gets an email
bounce, because jetty-users-requests is not a
Greg,
The requested info:
Server receives this (pardon the brackets):
URL[https://demo.jambo.software/demo.jambo.software/s;x=13y762q065p53vl8nbmb4uf720]
HEADER[sec-fetch-mode]=[cors]
HEADER[content-length]=[26]
HEADER[sec-fetch-site]=[same-origin]
HEADER[accept-language]=[en-US,en;q=0.9]
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