mraible opened a new pull request, #337:
URL: https://github.com/apache/roller/pull/337

   The 6.1.x version of #320, including its per-host cache keys and the save 
from an administrator's request.
   
   - `InitFilter` no longer keeps the first request's URL as the site URL for 
the whole application. Each request's URL is available on its own thread for 
that request, and `getAbsoluteContextURL()` falls back to it only while 
`site.absoluteurl` is unset, logging a warning once.
   - While it's unset, the page, feed, site-wide and planet caches include the 
request's URL in their keys, so content built for one host name is only served 
to requests for that host name, and caching keeps working.
   - The installer's bootstrap step, the first administrator's registration, 
and the first Roller UI request from a global administrator save 
`site.absoluteurl` when it's still unset. On an upgraded 6.1.x site, which runs 
no installer step, the first admin page view fills it in.
   - Request URLs keep the request's scheme and port, so HTTPS sites get 
`https://` links.
   
   For 6.1.8 specifically: the ping queue runs outside any request, so pings 
are skipped (with a warning) until `site.absoluteurl` is set, which the first 
admin page view does. `WebloggerRuntimeConfig.setAbsoluteContextURL` and 
`InitFilter.getAbsoluteUrl` are removed. CHANGES (#336) tells admins to set 
"Absolute URL to site".
   
   Changes from master: `Install` implements `ServletRequestAware` here, as on 
master, and the tests use `javax.servlet`.
   
   Tests: `InitFilterTest`, `InstallTest`, `RegisterSiteUrlTest` and 
`SiteUrlForAdminTest`. `mvn test` passes (546 run, 1 skipped), and the Selenium 
integration tests pass. The master version was measured on a copy of a 
production site: no difference between the setting set and empty.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to