Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.0.1-rc4
-
None
-
Fedora Core 2
Sun Java 1.4.2_05
Apache 2.0.5
mod_jk2 2.0.4
Tomcat 5.5.9
Description
While testing 1.0.1RC4, I did notice something was changed in the way
actionURL and renderURL was generated compared to 1.0.1RC2. It
appears like the portlet tags are now encoding the URLs to escape
characters such as slashes and so forth.
For example, an action URL that used to look like the following:
/vps/portal/vps-cms/_ac_vps-cms_row_col1_loginPortlet/AC/_pid/vps-cms_row_col1_loginPortlet
now looks like this:
/vps/portal/vps-cms%2F_ac_vps-cms_row_col1_loginPortlet%2FAC%2F_pid%2Fvps-cms_row_col1_loginPortlet
While this URL seems to work fine if you directly access tomcat, if
you try to acces to this URL through apache via jk2 bridge, apache
fails to parse the URL correctly and you get 404 error that looks like
this:
The requested URL
/vps/portal/vps-cms/_ac_vps-cms_row_col1_loginPortlet/AC/_pid/vps-cms_row_col1_loginPortlet
was not found on this server.
Although I think our configuration for apache and tomcat are pretty
much like the vanilla installation, I'd be happy to send you those
configuration files if you think it will help you with addressing the
issue.
The testing was done on
Fedora Core 2
Sun Java 1.4.2_05
Apache 2.0.5
mod_jk2 2.0.4
Tomcat 5.5.9
While I understand Pluto Driver is not meant to be used for production
quality, I would think this is something you guys might look into
investigating for further consideration.
Many thanks
Yujin