[jboss-jira] [JBoss JIRA] (WFLY-3036) Forwarded POST request becomes a GET request
Stuart Douglas (JIRA)
issues at jboss.org
Thu Feb 27 17:01:47 EST 2014
[ https://issues.jboss.org/browse/WFLY-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12948796#comment-12948796 ]
Stuart Douglas commented on WFLY-3036:
--------------------------------------
Your example does not build:
[ERROR] Failed to execute goal on project vaadin-cdi-example: Could not resolve dependencies for project com.vaadin:vaadin-cdi-example:war:1.0-SNAPSHOT: Could not find artifact org.peimari:maddon:jar:1.2 in central (http://repo.maven.apache.org/maven2) -> [Help 1]
> Forwarded POST request becomes a GET request
> --------------------------------------------
>
> Key: WFLY-3036
> URL: https://issues.jboss.org/browse/WFLY-3036
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Matti Tahvonen
> Assignee: Stuart Douglas
>
> POST requests that get forwarded (at least due to <security-constraint> rule) are reported as GET requests when the request arrives to the destination.
> Now e.g. Vaadin login UI that sends POST request (XHR) to the "original" address dies as Vaadin servlet returns html instead of JSON.
> The same setup works in JBoss 7.1 and Glassfish.
> The issue (and workaround) is describe in the github project:
> https://github.com/mstahv/vaadin-cdi-jaas-jbossas-example/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list