Quantcast
Channel: SCN : All Content - SAP NetWeaver Application Server
Viewing all articles
Browse latest Browse all 2997

SAP Webdispatcher - Http 400 Bad Request

$
0
0

Dear friends,

 

We have configured the SAML2.0 via SAP Web Dispatcher to the back-end SAP Enterprise Portal application.

 

We are running into the following issue when we make a call via SAP Web Dispatcher after the SAML2.0 Service Provider authentication.

 

400 Bad HTTP request

 

Bad HTTP request

 

Error:     -21

Version:     702

Component:     HTTP_FILTER

Date/Time:     Fri Jun 27 12:37:56 2014

Module:     http_auth_mt.c

 

 

In the Web Dispatcher logs, have found the details:

 

[Thr 140182570174208] Fri Jun 27 08:50:24 2014
[Thr 140182570174208] *** ERROR => Request URI too long, size=9136 [ictxxfilt_mt 188]
[Thr 140182570174208] *** ERROR => illegal request {0004f94a} [http_auth_mt.c 587]
[Thr 140182570174208] CONNECTION (id=4/129354):
    used: 1, type: default, role: Server(1), stateful: 0
    NI_HDL: 511, protocol: HTTPS(2)
    local host:  20.148.154.71:9444 ()
    remote host: 20.148.154.71:47879 ()
    status: READ_REQUEST
    connect time: 27.06.2014 08:50:23
    MPI request:        <18a0>   MPI response:        <18a1>
    request_buf_size:   65464    response_buf_size:   0
    request_buf_used:   11086    response_buf_used:   0
    request_buf_offset: 0        response_buf_offset: 0

[Thr 140182567003904] *** ERROR => Request URI too long, size=9142 [ictxxfilt_mt 188]
[Thr 140182567003904] *** ERROR => illegal request {0004f94b} [http_auth_mt.c 587]
[Thr 140182567003904] CONNECTION (id=4/129355):
    used: 1, type: default, role: Server(1), stateful: 0
    NI_HDL: 504, protocol: HTTPS(2)
    local host:  20.148.154.71:9444 ()
    remote host: 20.148.154.71:47881 ()
    status: READ_REQUEST
    connect time: 27.06.2014 08:50:24
    MPI request:        <18a2>   MPI response:        <18a3>
    request_buf_size:   65464    response_buf_size:   0
    request_buf_used:   11092    response_buf_used:   0
    request_buf_offset: 0        response_buf_offset: 0


Based on the above error, it seems the URI length is an issue.

 

Have you ever face this issue? If so, may I know the answer t fix this problem.

 

Much appreciated...

 

Thank you,

Sri


Viewing all articles
Browse latest Browse all 2997

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>