UIM 20.3.3 widget on StandAlone URL give HTTP Status 400 – Bad Request
search cancel

UIM 20.3.3 widget on StandAlone URL give HTTP Status 400 – Bad Request

book

Article ID: 218264

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When clicking on an alarm widget on StandAlone URL dashboard the browser gives HTTP Status 400 – Bad Request

If this is open from a browser that has NOT yet logged into the OC it will show the below. 

If you open the OC and then open this dashboard it just works fine. 

 

HTTP Status 400 – Bad Request


Type Exception Report

Message Invalid character found in the request target [/operatorconsole_portlet/standalone_login.jsp?viewOptions={%27minimal%27%20:%20%27true%27,%20%27disableLockedAlarmFilters%27%20:%20%27true%27,%20%27filters%27%20:%20[{%27field%27%20:%20%27hostname%27,%20%27operator%27%20:%20%27contains%27,%20%27not%27%20:%20%27false%27,%20%27value%27%20:%20%27lvn%27%20}]}&external=true&persistLogin=Bearer%20eyJhbGciOiJIUzI1NiJ9.eyJKV1RfVVNFUl9OQU1FX0NMQUlNIjoiYWRtaW5pc3RyYXRvciIsInN1YiI6IjEwMTU5IiwiSldUX0FDQ09VTlRfQ0xBSU0iOiIiLCJKV1RfUFJJTkNJUEFMX0NMQUlNIjoie1wibmFtZVwiOlwiYWRtaW5pc3RyYXRvclwiLFwicGFzc3dvcmRcIjpcIjQ1Nzc1MzQ1NzM3ODUwNzQyYjQ2NDk1ODY4NmE1NzQxNzUzNDMwNzI3NTRhNTk2MTUwNjQ3MDRlNzg2ZTZiNjkzNDRlNmUzMzY1NzE1MTM4MzIzNjUxM2RcIixcImFjbFwiOlwiU3VwZXJ1c2VyXCIsXCJwZXJtaXNzaW9uc1wiOltcIkVkaXQgTWFpbnRlbmFuY2UgTW9kZSBTY2hlZHVsZXNcIixcIlVTTSBNb2RpZnkgSW5kaXZpZHVhbCBNb25pdG9ycyBmb3IgQ29tcHV0ZXIgU3lzdGVtc1wiLFwiTGlzdCBEZXNpZ25lclwiLFwiU0xNIEFkbWluXCIsXCJSZWFzc2lnblwiLFwiVVNNIE1vZGlmeSBTaGFyZWQgQWxhcm0gRmlsdGVyc1wiLFwiRGlzY292ZXJ5IFBpZVwiLFwiTGF1bmNoIFVSTCBBY3Rpb25zXCIsXCJNYW5hZ2UgUHJvZmlsZXNcIixcIlByb2JlIFRlbXBsYXRlIEJhc2ljXCIsXCJEYXNoYm9hcmQgRGVzaWduZXJcIixcIkFsYXJtIE1hbmFnZW1lbnRcIixcIkRhc2hib2FyZCBEb3dubG9hZFwiLFwiT0MgR3JvdXAgRGVsZXRlXCIsXCJXQVNQXCIsXCJMaWNlbnNlIE1hbmFnZW1lbnRcIixcIlFvUyBBY2Nlc3NcIixcIkFjY291bnQgQWRtaW5pc3RyYXRpb25cIixcIkRhc2hib2FyZCBVcGxvYWRcIixcIk5GQSBWaWV3IFRvU1wiLFwiUHJvZ3JhbSBPcHR...]. The valid characters are defined in RFC 7230 and RFC 3986

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Invalid character found in the request target [/operatorconsole_portlet/standalone_login.jsp?viewOptions={%27minimal%27%20:%20%27true%27,%20%27disableLockedAlarmFilters%27%20:%20%27true%27,%20%27filters%27%20:%20[{%27field%27%20:%20%27hostname%27,%20%27operator%27%20:%20%27contains%27,%20%27not%27%20:%20%27false%27,%20%27value%27%20:%20%27lvn%27%20}]}&external=true&persistLogin=Bearer%20eyJhbGciOiJIUzI1NiJ9.eyJKV1RfVVNFUl9OQU1FX0NMQUlNIjoiYWRtaW5pc3RyYXRvciIsInN1YiI6IjEwMTU5IiwiSldUX0FDQ09VTlRfQ0xBSU0iOiIiLCJKV1RfUFJJTkNJUEFMX0NMQUlNIjoie1wibmFtZVwiOlwiYWRtaW5pc3RyYXRvclwiLFwicGFzc3dvcmRcIjpcIjQ1Nzc1MzQ1NzM3ODUwNzQyYjQ2NDk1ODY4NmE1NzQxNzUzNDMwNzI3NTRhNTk2MTUwNjQ3MDRlNzg2ZTZiNjkzNDRlNmUzMzY1NzE1MTM4MzIzNjUxM2RcIixcImFjbFwiOlwiU3VwZXJ1c2VyXCIsXCJwZXJtaXNzaW9uc1wiOltcIkVkaXQgTWFpbnRlbmFuY2UgTW9kZSBTY2hlZHVsZXNcIixcIlVTTSBNb2RpZnkgSW5kaXZpZHVhbCBNb25pdG9ycyBmb3IgQ29tcHV0ZXIgU3lzdGVtc1wiLFwiTGlzdCBEZXNpZ25lclwiLFwiU0xNIEFkbWluXCIsXCJSZWFzc2lnblwiLFwiVVNNIE1vZGlmeSBTaGFyZWQgQWxhcm0gRmlsdGVyc1wiLFwiRGlzY292ZXJ5IFBpZVwiLFwiTGF1bmNoIFVSTCBBY3Rpb25zXCIsXCJNYW5hZ2UgUHJvZmlsZXNcIixcIlByb2JlIFRlbXBsYXRlIEJhc2ljXCIsXCJEYXNoYm9hcmQgRGVzaWduZXJcIixcIkFsYXJtIE1hbmFnZW1lbnRcIixcIkRhc2hib2FyZCBEb3dubG9hZFwiLFwiT0MgR3JvdXAgRGVsZXRlXCIsXCJXQVNQXCIsXCJMaWNlbnNlIE1hbmFnZW1lbnRcIixcIlFvUyBBY2Nlc3NcIixcIkFjY291bnQgQWRtaW5pc3RyYXRpb25cIixcIkRhc2hib2FyZCBVcGxvYWRcIixcIk5GQSBWaWV3IFRvU1wiLFwiUHJvZ3JhbSBPcHR...]. The valid characters are defined in RFC 7230 and RFC 3986
 org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:490)
 org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:261)
 org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
 org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:893)
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1707)
 org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
 java.lang.Thread.run(Thread.java:748)

Note The full stack trace of the root cause is available in the server logs.

 

Environment

Release : 20.3

Component : UIM OPERATOR CONSOLE - DASHBOARDS/DESIGNER

Cause

Defect: DE502036

Issue is seen in UIM 20.3.3HF2 (June Patch) 

Resolution

The following 3 packages are to be deployed on top of UIM 20.3.3HF2 (June Patch) 

UIM HOTFIXES

 

ump_operatorconsole 2.10 HF4

https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU01897&os=MULTI-PLATFORM

ump_dashboard 20.3.3 HF2

https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU01895&os=MULTI-PLATFORM

wasp_alarmviewer_api 2.1.7 HF3

https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU01898&os=MULTI-PLATFORM