Hi Mallick, hi all, To me it appears this setting is ignored by tc 7.0.x. I created a servlet: protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { request.getSession().invalidate(); final int NUM_COOKIES = 500; for (int i = 0; i < NUM_COOKIES; i++) { Cookie c = new Cookie("foo" + i, UUID.randomUUID().toString()); response.addCookie(c); } response.setContentType("text/html"); response.getWriter().write( "

A ton of cookies

" ); System.out.println("sent " + NUM_COOKIES); } Accessing it causes the exception to be thrown. Whereas tc 6.0.33 behaviour is changed by increasing "maxHttpHeaderSize", 7.0.0, 7.0.14, 7.0.21 ignore the setting. i.e. for tc 6 setting maxHttpHeaderSize="8193" will cause OOB exception at index 8193. for tc 7 OOB always happens at 8192. I first blamed eclipse wtp doing sth. wrong when applying the configuration. Therefore, I checked the connector's jmx properties and to my surprise I could no longer find a property called "maxHttpHeaderSize" for the connector (comparing tc 6 to 7). Was it dropped by intention? I skimmed through the changelogs but couldn't find an explanation . . . Afaik as I know this is a configurable setting for (at least most) webservers Best Regards, Martin