GoogleCodeExporter
commented
9 years ago Howdy,
It isn't easy to fix the URL length at the moment. For a few reasons:
* there's a few places where static local buffers on the stack are used
* the 4k limit appears in other places - eg the in-memory buffer page size
(stmem);
the size that data is read back from the store
Bumping up the URL length without bumping up the others may cause subtle weird
issues
and I don't want to have to find/fix those just for now. Instead, I'd rather
work on
tidying up the store client / store memory cache code so it can handle arbitrary
sized buffers and URLs/headers which span >1 buffer; then just allow the URL
length
to be dynamic (with a max limit configured at runtime.)
But thanks for bringing this up. I'll start brain dumping exactly what needs to
happen in the code for this issue to go away so I/others have something to work
towards.Original comment by adrian.c...@gmail.com on 13 Apr 2010 at 12:44
- Added labels: Version-Head
- Removed labels: Version-1.0
Original issue reported on code.google.com by
pyroma...@gmail.comon 12 Apr 2010 at 9:25