Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preference Header Exception Handling #483

Closed
wants to merge 1 commit into from

Conversation

JefWight
Copy link
Contributor

This change adds some protection around invalid integers being passed in
for integer preference headers. If a client specifies null /
non-integer to "wait", for example, the current code would throw an
ArgumentNullException or FormatException. By properly throwing an
ODataException, service implementations can catch and return a correct
error to the client.

This resolves #92.
Fix #92

This change adds some protection around invalid integers being passed in
for integer preference headers.  If a client specifies null /
non-integer to "wait", for example, the current code would throw an
ArgumentNullException or FormatException.  By properly throwing an
ODataException, service implementations can catch and return a correct
error to the client.
@LianwMS
Copy link
Contributor

LianwMS commented Mar 15, 2016

submit with f32aa58

@LianwMS LianwMS closed this Mar 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parsing Preference headers with invalid values has unexpected results
3 participants