You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bridges-dev@portals.apache.org by "Ate Douma (JIRA)" <br...@portals.apache.org> on 2005/10/07 02:23:47 UTC
[jira] Assigned: (PB-13) Extra parameters injected into portlet request
[ http://issues.apache.org/jira/browse/PB-13?page=all ]
Ate Douma reassigned PB-13:
---------------------------
Assign To: Ate Douma
> Extra parameters injected into portlet request
> ----------------------------------------------
>
> Key: PB-13
> URL: http://issues.apache.org/jira/browse/PB-13
> Project: Portals Bridges
> Type: Bug
> Reporter: James Schopp
> Assignee: Ate Douma
> Priority: Minor
>
> The extra parameters "_spage", "_sorig", and "_kra" get added to the portlet request For some applications (IBM WebFacing, for example), these un-expected parameters cause issues. Allthough they may be necessary for the Struts bridge, they should be filtered out by the time the request reaches the actual portlet.
> I have solved this by creating a new RequestWrapper that filters these parameters (configurable in portlet.xml). The wrapper is created (and wrapped around the real request) in my ServletContextProvider.
> Ate, this may be something you consider app-specific, but it's pretty configurable, and there is no overhead if you do not configure any parameters to be filtered. So, it's more flexibility, with no drawbacks (and it get's it out of my code and into yours ;-)
> see: http://support.liferay.com/browse/LEP-529
> thanks, james
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org