You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2008/01/26 00:18:36 UTC
[jira] Commented: (SLING-126) MicrojaxPostServlet: redirect to
Referer if provided, unless ujax_redirect is provided
[ https://issues.apache.org/jira/browse/SLING-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562754#action_12562754 ]
Tobias Bocanegra commented on SLING-126:
----------------------------------------
i would add an additional step:
1.5) if POST url contains and extension, use this url.
> MicrojaxPostServlet: redirect to Referer if provided, unless ujax_redirect is provided
> --------------------------------------------------------------------------------------
>
> Key: SLING-126
> URL: https://issues.apache.org/jira/browse/SLING-126
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Currently, the Referer HTTP header is ignored for redirects, as MicrojaxPostServlet redirects to the created or modified node.
> Redirecting to the Referer is often useful in browser-based applications, to enable this I suggest the following logic:
> 1) If ujax_redirect parameter is given, redirect to that after the POST
> 2) else use the "Referer" HTTP header, if provided
> 3) else redirect to the Node that was created or modified.
> We might want to add a "magic" value (a star?) to ujax_redirect that says "use method 3) even if Referer is given", or "insert the path of the created/modified Node instead of the star"?
> For now, I'll implement the simple logic shown above, and we can refine if needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.