Timeline for "text/plain" content type header for x-www-form-urlencoded content? [duplicate]
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 2, 2018 at 21:21 | history | edited | user84207 | CC BY-SA 4.0 |
deleted 163 characters in body
|
| Nov 2, 2018 at 16:37 | comment | added | user84207 | Yes, I am aware of my own answer pointing out the new json endpoint in the doc. Thanks. | |
| Nov 1, 2018 at 22:14 | history | edited | Brock Adams |
See the linked duplicate.
|
|
| Nov 1, 2018 at 21:37 | comment | added | Brock Adams |
No. As already explained, x-www-form-urlencoded is not for server responses. You know what to expect because (A) The docs tell you exactly and (B), the page is in direct response to your POST. ... Also note that other general clients have no troulbe handling the Stack exchange API, even though it is non-conforming. (Nevertheless, the linked bug should be resolved.) Update: Turns out the FR/Bug was silently resolved last year. See the duplicate question.
|
|
| Nov 1, 2018 at 21:25 | review | Reopen votes | |||
| Nov 1, 2018 at 21:32 | |||||
| Nov 1, 2018 at 21:15 | history | edited | user84207 | CC BY-SA 4.0 |
edited tags
|
| Nov 1, 2018 at 21:08 | history | edited | user84207 | CC BY-SA 4.0 |
edited tags
|
| Nov 1, 2018 at 20:02 | history | closed | Brock Adams | Duplicate of Stack Exchange OAuth2, explicit access-token response format does not adhere to RFC6749 standard | |
| Nov 1, 2018 at 17:15 | history | edited | Brock Adams |
edited tags
|
|
| Nov 1, 2018 at 17:13 | answer | added | Brock Adams | timeline score: 0 | |
| Nov 1, 2018 at 7:40 | review | First posts | |||
| Nov 1, 2018 at 16:40 | |||||
| Nov 1, 2018 at 7:38 | history | asked | user84207 | CC BY-SA 4.0 |