1. Edit the jetty.xml in the default profile such that it is given a "requestHeaderSize" of 100. For example: <Set name= "requestHeaderSize" >100</Set> 2. Log into hawtio and poke around a bit. You'll note that you do not get any 413 parser full errors and won't see it reflected in the log. Such as: 16:24:08,545 | DEBUG | qtp533698501-72 | AbstractGenerator | 86 - org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 | sendError: 413 Request Entity Too Large: head 16:24:08,546 | DEBUG | qtp533698501-72 | ChannelEndPoint | 86 - org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 | oshut SCEP@6b56ae3a{l(/0:0:0:0:0:0:0:1:33284)<->r(/0:0:0:0:0:0:0:1:8181),s=1,open= true ,ishut= false ,oshut= false ,rb= false ,wb= false ,w= true ,i=0r}-{AsyncHttpConnection@1a4f469,g=HttpGenerator{s=4,h=0,b=-1,c=0},p=HttpParser{s=7,l=0,c=-3},r=0} 16:24:08,546 | DEBUG | qtp533698501-72 | HttpParser | 86 - org.eclipse.jetty.aggregate.jetty-all-server - 8.1.17.v20150415 | filled 100/100 One should get such errors, because a "requestHeaderSize" of 100 is too small to accommodate the incoming headers. In this case, Jetty is still using the default "requestHeaderSize" of 6k. 2. Now do the same as 1, but change the default jetty port from 0 to some other number like 8181. Now if you log into Hawtio and poke around, you'll get the 413 error indicating the new size of 100 is being honored.