yaws_api: Fix matching of Content-Type in `parse_post/1` #180

Merged
merged 1 commit into from Jul 23, 2014

Conversation

Projects
None yet
2 participants
@dumbbell
Contributor

dumbbell commented Jul 23, 2014

"application/x-www-form-urlencoded" can be followed by attributes, such
as "; charset=UTF-8".

yaws_api: Fix matching of Content-Type in parse_post/1
"application/x-www-form-urlencoded" can be followed by attributes, such
as "; charset=UTF-8".

vinoski added a commit that referenced this pull request Jul 23, 2014

Merge pull request #180 from yakaz/fix-contenttype-matching-in-yaws_api
yaws_api: Fix matching of Content-Type in `parse_post/1`

@vinoski vinoski merged commit bbbf5f2 into klacke:master Jul 23, 2014

@dumbbell dumbbell deleted the yakaz:fix-contenttype-matching-in-yaws_api branch Jul 23, 2014

jgrinstead pushed a commit to jgrinstead/yaws that referenced this pull request Apr 23, 2015

Merge pull request #180 from yakaz/fix-contenttype-matching-in-yaws_api
yaws_api: Fix matching of Content-Type in `parse_post/1`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment