Ticket #2313 (new defect)

Opened 9 years ago

Remove the <base> element

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.5.7
Component: CPSDefault Version: 3.5.1
Severity: normal Keywords:


Current CPS pages anchor the base url by using the <base> element. Putting the current base url in a <base> element is, by definition, useless, whereas it prevents adding a layer of reverse proxying to a CPS site.

If one has a CPS Site including a first reverse proxy, normally all generated URIs should be relative, maybe with absolute path, otherwise it's a bug. Say the base URL as seen from outside the first reverse proxy is http://first.example/

In that case, adding a second reverse proxy in front of that, to serve from  http://second.example/ does not work, because the <base> element forces the user agents to use http://first.example/. Of course this can work only if the path part of the portal URL is the same (in the examples, both are /).

Such kind of secondary reverse-proxying is useful to ensure continuity of service while changing domain names, for example.

Note: See TracTickets for help on using tickets.