Timeline for "text/plain" content type header for x-www-form-urlencoded content?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 7:34 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Nov 1, 2018 at 19:50 | comment | added | Brock Adams |
@user84207, the question was not clear because (1) you were getting an access_token, which is the whole point, (2) the question shows confusion about the purpose and use of x-www-form-urlencoded, (3) you listed no actual practical problem. Contrast this to the linked bug report.
|
|
| Nov 1, 2018 at 19:47 | history | edited | Brock Adams | CC BY-SA 4.0 |
added 3 characters in body
|
| Nov 1, 2018 at 19:14 | comment | added | user84207 | I don't understand why the stackexchange API would use this custom non-standard response format instead of a standard JSON object that most REST api libraries understand. Also inconsistent with most of the rest of the API which uses JSON. | |
| Nov 1, 2018 at 18:58 | comment | added | user84207 | sorry, what isn't clear about the question? is there skepticism about whether the API actually sends back the content-type and response as stated? | |
| Nov 1, 2018 at 18:42 | history | edited | Brock Adams | CC BY-SA 4.0 |
deleted 5 characters in body
|
| Nov 1, 2018 at 18:36 | history | edited | Brock Adams | CC BY-SA 4.0 |
deleted 5 characters in body
|
| Nov 1, 2018 at 18:31 | history | edited | Brock Adams | CC BY-SA 4.0 |
added 849 characters in body
|
| Nov 1, 2018 at 17:13 | history | answered | Brock Adams | CC BY-SA 4.0 |