Skip to Content
avatar image
Former Member

400 Bad HTTP request: path too long

Dear Community,

I got the following error, while sending a http request with more than 4096 Bytes via ODATA to the Netweaver AS.

Technical information:

Netweaver without J2EE service

Regards,


Frank

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jun 05, 2014 at 02:30 PM

    Not the same case, but may trigger some solution:

    This problem occurs if you are using HTTP GET request instead of HTTP POST request. For the HTTP  GET request, there's a length restriction of around 2000 characters.
    So, it should work fine if you're switching the HTTP request method from the outdated GET to the recommend POST method. For the POST request there's no limitation in overall length/size.

    Please go to iView portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi.bex3x and change property "HTTP Request Method" to "HTTP: POST". Then try again.

    You can also find it using the following path:

    Content Administration -> Portal Content -> Content provided by SAP ->Platfrom Add-Ons -> Business Intelligence -> iViews -> BEx web (the second one with 3x at
    the end of the iView ID)

    Also see the note about the GET POST:
    1492282 - How to realize passing parameters in Java Web using POST

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 05, 2014 at 02:56 PM

    Sorry, I forgot to mention that I am using HTTP:POST and that the max path size, which doesnt throw an error, is 4096. 

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 06, 2014 at 04:42 PM

    Hello Frank,

    The maximum URL length in NW AS ABAP is hard-coded to 4096. This is seen as a reasonable approach since most Web Browsers have difficulties themselves with very long URLs. You can find an extensive discussion here:

    http://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers

    In your case, you probably do not have a browser on the client side. However, I think it is good practice in general to avoid lengthy URLs since they might also cause issues with intermediary devices such as proxys, load balancers etc.

    Regards,

    Tobias

    Add comment
    10|10000 characters needed characters exceeded