[Typo3-dev] To long BE URLs: POST/GET discussion

Stefan Kreisberg stefanNOSPAM at linkfactory.dk
Thu May 26 15:05:22 CEST 2005


Hiya,

I dunno whether this issue has ever been discussed, so here's some thoughts
on the BE behaviour, long URI's and Apache server:

I have a site that changes a lot of content and many new pages each week.
The editors and admins like to clear their info cache with regards to
getting resetting search results for various issues. This leads to many
records in the related tables, which again leads to "higher" (and thus also
bigger) id's with the auto_inc. The result is, that eventually the
recursive call to "clear info cache" is so long that a default Apache
compilation fails with:

 Request-URI Too Large
 The requested URL's length exceeds the capacity limit for this server.
 
 request failed: URI too long
 
One could ofcourse recompile/tune Apache with a larger
DEFAULT_LIMIT_REQUEST_LINE but wouldn't it be better to change the
behaviour of T3 BE to either post the request or to re-design/re-use MySQL
id's when all info cache is deleted (which I guess BTW perhaps is a part of
the new indexed searcher?)

I don't consider this a T3 bug so I haven't registerede anything there -
it's more a Apache limitation that T3 doesnt take into account, and not
realy a major issue... 

If anyone knows of this issue/someone has discussed it before with some
smarter conclusions than mine - I'd like to hear ofcourse ;-D

Cheers and rgs,

-Stefan a.k.a. strato




More information about the TYPO3-dev mailing list