When accessing directly Tomcat, the resolved source URL can contain an extra port

View issue · Add comment

Issue created

Thomas Mortagne created this issue on 06/Aug/24 10:37

Summary:	When accessing directly Tomcat, the resolved source URL can contain an extra port
Issue Type:	Bug
Affects Versions:	14.10.21
Assignee:	Unassigned
Components:	Containers
Created:	06/Aug/24 10:37
Priority:	Major
Reporter:	Thomas Mortagne
Description:	Not sure if it depends on the version of Tomcat or the Servlet API. But recent versions of Tomcat don't make the difference between explicitly indicated port or not in ServletRequest#getServerPort() (which is what we currently use as fallback). We need to find a more optimized trick for this use case (direct access to Tomcat without going through an HTTP proxy).

1 update

Changes by Thomas Mortagne on 06/Aug/24 10:37

Description:

Not sure if it depends on the version of Tomcat or the Servlet API. But recent versions of Tomcat don't make the difference between explicitly indicated port or not in ServletRequest#getServerPort() (which is what we currently use as fallback). We need to find a more optimized trick for this use case (direct access to Tomcat with default http or https port without going through an HTTP proxy).

This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)

If image attachments aren't displayed, see this article.