Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Update OptionIteratorExt::extract_location to comply with RFC7252 section 5.10.7 #6

Open
darconeous opened this issue Aug 26, 2019 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers P2 Priority 2

Comments

@darconeous
Copy link
Contributor

The relevant portion of RFC7252 section 5.10.7 is the last paragraph (emphasis mine):

The options that are used to compute the relative URI-reference are collectively called Location-\* options. Beyond Location-Path and Location-Query, more Location-\* options may be defined in the future and have been reserved option numbers 128, 132, 136, and 140. If any of these reserved option numbers occurs in addition to Location-Path and/or Location-Query and are not supported, then a 4.02 (Bad Option) error MUST be returned.

Currently we are ignoring options 128, 132, 136, and 140. This must be fixed to be in compliance with RFC7252.

@darconeous darconeous added bug Something isn't working P2 Priority 2 labels Aug 26, 2019
@darconeous darconeous added the good first issue Good for newcomers label Jan 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working good first issue Good for newcomers P2 Priority 2
Projects
None yet
Development

No branches or pull requests

1 participant