[Bodington-developers] Abolute URLs - Bug or Bug Fix?

[Jon M. <jo...@te...>]

I've found a feature in 2.6 which for me is a bug but may be a bug fix 
from someone else's point of view!

The login templates need to use absolute URLs at various points and 
these are built in methods of Facility.  They used to use the server 
name and the port numbers in bodington.properties but now they seem to 
always use the server name found in the HTTP request and only use the 
port numbers for the jump between http and https and back.  I don't 
really understand what the advantages of all this are but I can see 
several disadvantages, one of which is preventing me setting up 
Bodington the way I want.

1) Many servers have multiple IP name aliases and this is not a problem 
with Bodington when non-secure connections are made. However, when a 
secure connection is made the server name really needs to match the IP 
name in the server's digital certificate to prevent worrying error 
messages about the security popping up in the user's browser.  This 
seems to be broken - the correct port is used but not the correct IP name.

2) I'm using a single Apache installation to front end multiple 
Tomcats.  This is done with virtual hosting in Apache, URL rewriting and 
proxying.  So Apache accepts requests on port 80 and uses the server 
name in the request to identify which tomcat installation to use.  Each 
Tomcat listens on its own network ports on the localhost device only and 
Apache operates like a proxy - the URL is transformed by mapping the 
server name to localhost and the port number corresponding to the right 
Tomcat installation. Apache fetches the page and sends it to the client.

This is now broken by Bodington - you can log in O.K. (because tomcat 
and Apache are on the same server) but when you follow the link to the 
originally requested URL it's on the wrong port because it is 
constructed from the request headers formed by the proxy instead of from 
bodington.properties.  E.g. the user asks for 
http://myserver.com/bodington/site/ but Apache connects to tomcat using 
http://myserver.com:8080/bodington/site/ so after logging the later link 
is present on the page when it should be the former.

So, is this a bug or is it a bug fix?

Jon