Timeline for Got a Bad Status Line
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 12, 2015 at 2:02 | comment | added | Brock Adams | Official SE response is pretty nonexistent these days here on Stack Apps. ... Also, I have not noticed any change in throttling. My apps typically use small bursts of requests at about 2 per second. They still receive the backoff flag before any other failure. ... It may be that it's just you. But we'll never know without a proper question or unless an SE dev comes in from the cold (which seems unlikely) | |
| Aug 11, 2015 at 22:02 | comment | added | Dennis Williamson | ... I was hoping that an SE person would repond to my support tag and give an official response regarding changes in throttling. | |
| Aug 11, 2015 at 22:02 | comment | added | Dennis Williamson | @BrockAdams: I had done as you suggested and used Wireshark. There was no backoff message (which my code handles) and there was no HTTP response code (after receiving a bunch of 200s during each run) to handle. I think it's the silent failure that is SE's response when it believes you're being abusive. It hadn't found my pace to be abusive for the previous 16 months so I believe there has been an unannounced change on SE's part. I'll add silent-failure detection so that it waits and tries again. No MCVE will be forthcoming, I'm afraid, since I don't have time to do the "M" part. Sorry. ... | |
| Aug 11, 2015 at 18:29 | comment | added | Brock Adams | In that case, the code probably wasn't handling status and backoff flags correctly in the first place. Still need that MCVE. | |
| Aug 11, 2015 at 16:34 | history | answered | Dennis Williamson | CC BY-SA 3.0 |