# Whats the use of large\_client\_header\_buffers if client\_header\_buffer\_size exist?

**URL:** <https://www.ruby-forum.com/t/whats-the-use-of-large-client-header-buffers-if-client-header-buffer-size-exist/218204>\
**Category:** NGINX\
**Created:** [March 24, 2012, 1:45am UTC](https://www.ruby-forum.com/t/whats-the-use-of-large-client-header-buffers-if-client-header-buffer-size-exist/218204 "2012-03-24T01:45:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [March 24, 2012, 1:45am UTC](https://www.ruby-forum.com/t/whats-the-use-of-large-client-header-buffers-if-client-header-buffer-size-exist/218204/1 "2012-03-24T01:45:09Z")

</div>

Hello All!

Suppose I have client\_header\_buffer\_size to 1k;  
… And i dont want anything to be sent past 1k… Why  
would i ever have the need to use the large… variable? Is it like  
having the possibility of “bursting” up to the value of  
“large\_client\_header\_buffers” variable?

What so special with the large\_client\_header\_buffers that I cannot  
define it within a server {} … on the contrary I can use  
client\_header\_buffer\_size inside the a {} and locations… ?

Regards,  
Mike