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

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).