Forum Discussion

jnunham_332885's avatar
jnunham_332885
Icon for Altostratus rankAltostratus
Sep 14, 2017

HTTP headers too long error message

Hello,

 

I'm trying to run a REST API call to add a node to multiple pools. There are about 30 - 40 pools I'm trying to add the node to. When I run my command to add the node to the pool list, I'm getting the following error message:

 

{"code":400,"message":"HTTP headers too long!","errorStack":[]}

If I shorten the amount of pools I'm trying to add the node to, it works without issue. From my research, I believe that the POST method itself has no limitations as to how much data you can send. It sounds like whatever web server on the receiving end is the thing that determines how big of a payload it will accept in a POST. Is there a way to override the default F5 limitation or specify in my POST some way to extend how much it can accept? I would really like to be able to add nodes to a large amount of pools in a single POST instead of having to break it up in to chunks.

 

Thank you!

 

devops
iControlREST
  • Satoshi_Toyosa1's avatar
    Satoshi_Toyosa1
    Ret. Employee
    Sep 26, 2017

    The error message 

    HTTP headers too long
    suggests that your request has quite long header field(s). Although HTTP RFCs do not clearly stipulate a maximum allowed length for a header field or a maximum number of the header fields (to my knowledge), normally, an HTTP server implementation enforces a certain limit. My casual test suggests that the limit is somewhere around 4000 bytes (I sent a very long User-Agent value).

    Will you post the exact request and reply? Please include the complete header sections and body for both. Copy&paste of the curl commands you execute would be helpful. If the data is too long to post, you can truncate: but please add the number of bytes.

    You stated that the amount of data (which is the body part of the HTTP request) sent in the 

    POST
    request might be too large, so the error message might be a red herring, though.