Opened 10 years ago
Closed 10 years ago
#562 closed defect (worksforme)
Proxied location not used in permalink
Reported by: | Twan Goosen | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | VLO-3.0.1 |
Component: | VLO web app | Version: | VLO-3.0 |
Keywords: | Cc: | teckart@informatik.uni-leipzig.de |
Description
The permalink in VLO 3.0 generates links like:
Even though this is a valid location, it is not preferable as the internal location might change. Instead, the location in the example should be replaced with:
This may be fixable in the server configuration, but may also need changes in the codebase. Investigate.
Change History (4)
comment:1 Changed 10 years ago by
Cc: | teckart@informatik.uni-leipzig.de added |
---|
comment:2 Changed 10 years ago by
comment:3 Changed 10 years ago by
Wicket constructs the URL by (amongst other things) calling httpServletRequest.getContextPath(). Can this be influenced?
(Specifically it appends protocol, host, port, context path, filter path, then joins this with the in-application path, e.g. 'search', see org.apache.wicket.request.UrlRenderer)
comment:4 Changed 10 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
LatAdmin have found a way to fix this by changing the apache configuration. This has been tested for the VLO beta location. No need to adjust the application.
The following happens on catalog (some notes in Dutch copied from an e-mail to latadmin@mpi.nl):
http://catalog.clarin.eu/vlo
De Tomcat weet (dankzij AJP, vermoed ik) dat hij via de connector wordt benaderd en via welk extern adres. Het feit dat daarvóór nog een proxy zit wordt niet verwerkt. Weten jullie of het mogelijk is om deze informatie op een elegante manier door te geven. Concreet dus, om de Tomcat zover te krijgen dat hij denkt dat de VLO web app op http://catalog.clarin.eu/vlo draait i.p.v. http://catalog.clarin.eu/vlo1/vlo.
De ultieme fallback is de externe locatie configurabel maken d.m.v. een context parameter maar dat doe ik natuurlijk liever niet.