You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/03/26 15:25:00 UTC

[jira] [Commented] (WICKET-7152) Extend RedirectRequestHandler for statusCodes 307 and 308

    [ https://issues.apache.org/jira/browse/WICKET-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938640#comment-17938640 ] 

ASF GitHub Bot commented on WICKET-7152:
----------------------------------------

hosea opened a new pull request, #1133:
URL: https://github.com/apache/wicket/pull/1133

   https://issues.apache.org/jira/browse/WICKET-7152




> Extend RedirectRequestHandler for statusCodes 307 and 308
> ---------------------------------------------------------
>
>                 Key: WICKET-7152
>                 URL: https://issues.apache.org/jira/browse/WICKET-7152
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket-core
>    Affects Versions: 10.4.0
>            Reporter: Hans Schäfer
>            Priority: Minor
>
> RedirectRequestHandler only accepts status 301, 302 and 303. Should also work for other status codes 307 and 308.
> 308 makes the browser use the same HTTP-Method. So if a browser sends a POST-Request and receives a 308-Response, then the browser will repost for the changed location. I need this behavior for supporting an endpoint used by another company. My workaround until now is an Apache-Rule doing the job now.
> Note: If it was a 302 the browser would change the method to "GET". 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)