Skip to content
This repository has been archived by the owner on Jul 16, 2019. It is now read-only.

application/x-www-form-urlencoded; charset=UTF-8 is resolved as CORSRequestType.ACTUAL instead of CORSRequestType.SIMPLE #3

Open
ronaldploeger opened this issue Sep 10, 2013 · 2 comments

Comments

@ronaldploeger
Copy link

Hi,

when the contentType of a request is set to "application/x-www-form-urlencoded; charset=UTF-8" the request is resolved to be a CORSRequestType.ACTUAL instead of a CORSRequestType.SIMPLE because of the charset part in the content-type.

Currently it does not seem to matter because you are calling this.handleSimpleCORS(request, response, filterChain); in both cases but I was wondering if this is correct in general an might lead to bugs later on.

Best regards,
Ronald

@mohitsoni
Copy link
Contributor

This behavior is incorrect, and is a bug. I'll fix it, and roll out a new version soon. Thanks for reporting it.

@ronaldploeger
Copy link
Author

Thank you very much for your work and for providing this filter!

Ronald

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants