Forum Discussion

Maurice_G_'s avatar
Maurice_G_
Icon for Employee rankEmployee
Jun 17, 2010

POST generates bad request when accelerated

I recently moved an application from big-ip 9.3.1 to big-ip 10.2.9 with WAM. Some HTTP POST get a 400 response from big-ip with WAM. I can workaround the issue by disabling CACHE for such requests. Does anybody have an idea why the WAM would cause such behavior?

8 Replies

  • In general it varies. But the one that generated the error used Chunked Transfer Encoding...the length was 1570 bytes.
  • Nicolas_Berthie's avatar
    Nicolas_Berthie
    Historic F5 Account
    POST + Chunked Transfer Encoding sounds not very good. I would recommand to use an iRule to bypass WAM for POST request :

     

     

    when HTTP_REQUEST {

     

    if {[HTTP::method] equals "POST"}{

     

    WAM::disable

     

    }

     

    }
  • Could you disable WAM only for POST requests with a transfer-encoding of chunked?

     

     

    Aaron
  • Thanks so much for your response. I could but I am trying to understand why I need to do this? What exactly is causing the bad request for this POST?
  • Thanks so much for your response. I did just this but I am trying to understand why I need to do this? What exactly is causing the bad request for this POST?
  • I'm not sure why it would happen. I'd suggest opening a case with F5 Support to get help diagnosing the issue. In the meantime, as a workaround, you could disable WAM for chunked requests.

     

     

    Aaron
  • I did open a ticket and have tried to reproduce the issue but cannot. Support has provided a workaround and is looking for the issue to be reproduced in order to take it further.