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 api-v2.2
Search options not deleted
user 171
For questions relating to version 2.2 of the Stack Exchange API.
4
votes
0
answers
122
views
Byte Order Mark suddenly appearing in query results
Query results seem to have started including BOMs sometime today. I had to add code to handle it.
I don't see this documented anywhere.
3
votes
1
answer
998
views
Got a Bad Status Line
Since about 10 AM US-CDT on August 8, 2015, I've been getting
('http protocol error', 0, 'got a bad status line', None)
on a /users/{ids}/associated query after several successful such queries exec …
1
vote
Got a Bad Status Line
I suspect some new throttling kicked in on Saturday. When I slightly increased the delay between page= queries, the problem went away.