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 support
Search options not deleted
user 171
You need help with the use of the Stack Exchange API, apps built on the API, or assistance building scripts that work on Stack Exchange websites.
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.
1
vote
display_name isn't always there (should have OpenID name if needed)
Some users don't have display names.
Related:
User search doesn't work when name field is empty