Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with status-completed
Search options not deleted
user 55905
Indicates that a feature request has been implemented, a bug has been fixed, or another type of request has been processed.
-3
votes
1
answer
892
views
"text/plain" content type header for x-www-form-urlencoded content? [duplicate]
I'm getting the following response body and header from https://stackoverflow.com/oauth/access_token when attempting to
exchange an oauth code for a token:
<DEBUG> [00:30:03] my-app - content-type: …
- 115
2
votes
Stack Exchange OAuth2, explicit access-token response format does not adhere to RFC6749 stan...
I had the same problem. According to the authentication docs‡:
In order to get access_token and expires (if applicable) wrapped in a
JSON object, POST to https://stackoverflow.com/oauth/ …
- 115