[
https://issues.apache.org/jira/browse/JSPWIKI-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540576
]
Jürgen Weber commented on JSPWIKI-22:
-------------------------------------
As concerning baseURL determination, I think less necessary parameters the
better. If you need an information in init() that you cannot get until the
first doGet() do a lazy initialization in doGet().
Concerning the proxy argument for baseURL:
"RFC 1945 5.1.2 Request-URI
The Request-URI is a Uniform Resource Identifier (Section 3.2) and
identifies the resource upon which to apply the request."
So a proxy should not change the resource identification. In j2ee container,
the part after the slash always denotes the context.
getServletPath() and getContextPath() must deliver baseURL, else the j2ee
dispatching to web apps would not work.
A proxy should be transparent, so the web container should work regardless of
being behind a proxy or not.
So, if a proxy or firewall or loadbalancer is not transparent, the work-around
for this should not be a default, but rather a fix for only those needing it.
> 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.
