Timeline for URL Length Limit For For Requests Taking Vectorised Ids (/answers/{id}, /questions/{id}, etc)
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 13, 2015 at 9:45 | comment | added | Lutz Prechelt | @SamB: 406 "not acceptable". w3.org/Protocols/rfc2616/rfc2616-sec10.html | |
| May 1, 2011 at 1:59 | comment | added | SamB | A 4006 error? | |
| Jun 9, 2010 at 4:32 | vote | accept | Igor Zevaka | ||
| Jun 9, 2010 at 4:08 | comment | added | Kevin Montrose | @Igor - I believe asp.net defaults to 260 for the path, and something like 1k for query strings. This isn't spec'd in the API because we'll change it whenever we please - for one, .NET 4 knocks that up iirc - and relying on it isn't supported. If you receive 400s you suspect are because of path constraints, split into two and try again. Sorry there isn't a better solution. | |
| Jun 9, 2010 at 3:43 | comment | added | Kevin Montrose | @Igor - that is not a consensus, as default ASP.NET installations apparently do not behave that way. Your question is unanswerable anyway, as we can't give a limit in terms of number of ids when the limit is determined by the number of bytes in the url. | |
| Jun 9, 2010 at 3:30 | comment | added | Igor Zevaka | I appreciate the fact that giant URLs are not reliable and vendor specific, but the general consensus is that under anything 1000 characters is OK with most servers in their default configuration. My understanding is that Stack api sites have a more aggressive configuration where a 460 character request fails. | |
| Jun 9, 2010 at 3:16 | history | answered | Kevin Montrose | CC BY-SA 2.5 |