[
https://issues.apache.org/jira/browse/JSPWIKI-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540581
]
Janne Jalkanen commented on JSPWIKI-22:
---------------------------------------
Nope. Cannot do it lazily. We need it before any GET requests to set up e.g.
RSS generation (which creates a static file for performance reasons).
It used to be a fix for those who needed it (e.g. people with stunnel), but
since then it's turned out to be too useful. It's theoretically possible to
rip it out, but I wouldn't start doing it now... We would need to change our
entire URL generation schemes, RSS generation, and probably many, many other
things as well.
What I mean my proxy is that the host name may change. Or to be more probable,
the port in which the app is running may be different. For example, with basic
forwarding the servlet container might think it's running in port 8080, but the
outside world sees it in port 80. The context path would therefore be wrong.
This is typical in quite a few apache setups which for some reason or another
are not using mod_jk or mod_proxy.
> ShortURLConstructor broken
> --------------------------
>
> Key: JSPWIKI-22
> URL: https://issues.apache.org/jira/browse/JSPWIKI-22
> Project: JSPWiki
> Issue Type: Bug
> Components: Core & storage
> Affects Versions: 2.6.0
> Environment: apache-tomcat-6.0.14, java 6, XP
> Reporter: Jürgen Weber
> Priority: Blocker
> Fix For: 2.6.0
>
>
> Downloaded 2.5.149, unpacked with core pages, ran, fine.
> Changed jspwiki.urlConstructor to ShortURLConstructor.
> Now, navigation is broken: there is one wike element in the URL too much,
> also it seems the css cannot be found.
> http://localhost:8080/JSPWiki/wiki/wiki/OneMinuteWiki
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
