[Varnish] #455: Make HTTP_HDR_MAX a ./configure option

Varnish varnish-bugs at projects.linpro.no
Sun Feb 22 17:33:48 CET 2009

#455: Make HTTP_HDR_MAX a ./configure option
 Reporter:  whocares     |       Owner:  phk        
     Type:  enhancement  |      Status:  new        
 Priority:  normal       |   Milestone:             
Component:  varnishd     |     Version:  trunk      
 Severity:  normal       |    Keywords:  max headers
 While test driving varnish we ran into the "503 if too many headers
 received from backend" problem. Now, I don't want to start a discussion
 about how many headers a backend application may / should send. But it
 would be really nice if this could be configured while buildling varnish,
 so that I wouldn't have to patch up the code for every new release/build.
 Making HTTP_HDR_MAX configurable by the user (with a sensible default and
 also a sensible cap) would "solve" this problem for those users for whom
 the default just isn't enough and who can't fix the backend app (like in
 my case, closed software, no chance to fix anything :-().
 So, an --with-max-header-fields=<num> option to the configure script would
 be highly appreciated.

Ticket URL: <http://varnish.projects.linpro.no/ticket/455>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list