| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…rmat (OAI#5332) In JSON, property keys are always strings; in YAML they may or not be depending on the parser, but other formats may also be in use (TOML, TOON etc). What matters is the resulting type(s) of the decoded data, not the specific formatting used for the serialized form.
Appendix D no longer talks about percent-encoding of headers, as the specification is now clear that percent-encoding of headers is never done (with the exception of the use of style:form in Cookie headers).
We are specifically talking about the "encoding" keyword here, and the multipart/form-data media-type (most other multipart types decode to arrays).
This change is accompanied by an edit to the "Forms" page in the Media-Type Registry.
|
All the source PRs from v3.3 have been merged now, so this is ready to go. I edited each commit to indicate the original PR it came from. |
Sorry, something went wrong.
|
..and in comparing the diff of this branch vs v3.3-dev, it looks like nothing was missed -- the only differences from 3.3 are in the new security changes, and my two PRs that tweak the handling of multipart messages (#5407 and #5391). |
Sorry, something went wrong.
|
@karenetheridge Were there any merge conflicts when porting these that you had to resolve? |
Sorry, something went wrong.
|
No conflicts. |
Sorry, something went wrong.
There was a problem hiding this comment.
One thing which might just be me misunderstanding/misremembering.
Sorry, something went wrong.
..and be more specific about what an "array property" and "array schema" are
v3.2: fix whitespace (mistakenly added in #5420)
| Back | FazBrowse Home | New Git URL |
Backports from 3.3 to 3.2 of recent spec edits.
Will continue populating this list until all 3.3 PRs are merged.
I think all of these are suitable for inclusion into 3.2.1, as they are all clarifications rather than introducing new capabilities.