[rt-users] rt shredder slow

[Brumm, Torsten / Kuehne + Nagel / Ham MI-ID]

>From RFC 2616:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.2

The HTTP protocol does not place any a priori limit on the length of a URI.
Servers MUST be able to handle the URI of any resource they serve, and
SHOULD be able to handle URIs of unbounded length if they provide GET-based
forms that could generate such URIs. A server SHOULD return 414 (Request-URI
Too Long) status if a URI is longer than the server can handle (see section
10.4.15). 

      Note: Servers ought to be cautious about depending on URI lengths
      above 255 bytes, because some older client or proxy
      implementations might not properly support these lengths.

Try the cli based shredder, its much faster!


Kuehne + Nagel (AG & Co.) KG, Geschaeftsleitung: Hans-Georg Brinkmann (Vors.), Uwe Bielang (Stellv.), Bruno Mang, Dirk Blesius (Stellv.), Alfred Manke, Christian Marnetté (Stellv.),  Mark Reinhardt (Stellv.), Jens Wollesen, Rainer Wunn, Sitz: Bremen, Registergericht: Bremen, HRA 21928, USt-IdNr.: DE 812773878, Persoenlich haftende Gesellschaft: Kuehne & Nagel A.G., Sitz: Contern/Luxemburg Geschaeftsfuehrender Verwaltungsrat: Klaus-Michael Kuehne



________________________________

Von: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] Im Auftrag von Asif Iqbal
Gesendet: Sonntag, 3. Mai 2009 16:13
An: rt-users Users
Betreff: Re: [rt-users] rt shredder slow



On Sun, May 3, 2009 at 9:29 AM, Asif Iqbal <vadud3 at gmail.com> wrote:


	rt shredder part of rt 3.8.2 seems extremely slow in wiping out tickets. I have over thousand tickets that needs to be wiped out.
	
	can I any way speed up rt shredder? also how can I run it through cron?


When I pick 1000 as the limit for shredder I get this message


 



	
	

	Request-URI Too Large


	The requested URL's length exceeds the capacity limit for this server.


Hmm.. should I not able to shred 1000 ticket at once?
 


		-- 
	Asif Iqbal
	PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
	A: Because it messes up the order in which people normally read text.
	Q: Why is top-posting such a bad thing?
	
	
	




-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?