HTTP Status 400 – Bad Request

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

HTTP Status 400 – Bad Request

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
HTTP Status 400 – Bad Request
HTTP Status 400 – Bad Request
2021-05-28 12:23:06 - last edited 2021-06-04 03:20:27
Model: OC200  
Hardware Version:
Firmware Version:

Hi,

 

I encountered and error in OMADA controller OC200. I could not print created vouchers as I encountered an error when I am about to print them:

 

 

HTTP Status 400 – Bad Request

Type Exception Report

Message Invalid character found in the request target [/omada/3.2.3/hotspot/static/printVoucher.html?type=include&id[]=60006793ded39a066906e793&id[]=60006793ded39a066906e7b0&id[]=60006793ded39a066906e7b3&id[]=60a9a6f2ded39a0669ebc360&id[]=60a9a6f2ded39a0669ebc361&id[]=60a9a6f2ded39a0669ebc362&id[]=60a9a6f2ded39a0669ebc363&id[]=60a9a6f2ded39a0669ebc364&id[]=60a9a6f2ded39a0669ebc365&id[]=60a9a6f2ded39a0669ebc366&id[]=60a9a6f2ded39a0669ebc367&id[]=60a9a6f2ded39a0669ebc368&id[]=60a9a6f2ded39a0669ebc369&token=2c0cd1ba3be04541a86e66647f0f8d93&serverKey=15F3D81293D89A59B4D213FD44C5100FC215EBFF]. 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 [/omada/3.2.3/hotspot/static/printVoucher.html?type=include&id[]=60006793ded39a066906e793&id[]=60006793ded39a066906e7b0&id[]=60006793ded39a066906e7b3&id[]=60a9a6f2ded39a0669ebc360&id[]=60a9a6f2ded39a0669ebc361&id[]=60a9a6f2ded39a0669ebc362&id[]=60a9a6f2ded39a0669ebc363&id[]=60a9a6f2ded39a0669ebc364&id[]=60a9a6f2ded39a0669ebc365&id[]=60a9a6f2ded39a0669ebc366&id[]=60a9a6f2ded39a0669ebc367&id[]=60a9a6f2ded39a0669ebc368&id[]=60a9a6f2ded39a0669ebc369&token=2c0cd1ba3be04541a86e66647f0f8d93&serverKey=15F3D81293D89A59B4D213FD44C5100FC215EBFF]. 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:888)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1597)
	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.

Apache Tomcat/9.0.41

 

For your immediate assistance please.

 

Thanks!

  0      
  0      
#1
Options
1 Accepted Solution
Re:HTTP Status 400 – Bad Request-Solution
2021-06-03 07:35:21 - last edited 2021-06-04 03:20:27

Dear @john.redcat,

 

john.redcat wrote

Yes is it ok for print unused voucher, but when I print through selective printing, that error occurs

 

Thank you for your valued feedback. I've reported the issue to the R&D team for further investigation.

 

Update: The issue has been fixed now. Please confirm it.

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#11
Options
11 Reply
Re:HTTP Status 400 – Bad Request
2021-05-29 15:27:16 - last edited 2021-05-31 03:22:30

@john.redcat To TPLINK team, For  assistance please

  0  
  0  
#2
Options
Re:HTTP Status 400 – Bad Request
2021-05-31 03:27:32

Dear @john.redcat,

 

john.redcat wrote

I encountered and error in OMADA controller OC200. I could not print created vouchers as I encountered an error when I am about to print them:

HTTP Status 400 – Bad Request

 

What's the current firmware version of your OC200, please?

 

Did you access the Hotspot manager to print vouchers via cloud access (by visiting https://omada.tplinkcloud.com/)?

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#3
Options
Re:HTTP Status 400 – Bad Request
2021-06-01 02:40:20

@john.redcat same issue here

john.redcat wrote

Hi,

 

I encountered and error in OMADA controller OC200. I could not print created vouchers as I encountered an error when I am about to print them:

 

 

HTTP Status 400 – Bad Request

Type Exception Report

Message Invalid character found in the request target [/omada/3.2.3/hotspot/static/printVoucher.html?type=include&id[]=60006793ded39a066906e793&id[]=60006793ded39a066906e7b0&id[]=60006793ded39a066906e7b3&id[]=60a9a6f2ded39a0669ebc360&id[]=60a9a6f2ded39a0669ebc361&id[]=60a9a6f2ded39a0669ebc362&id[]=60a9a6f2ded39a0669ebc363&id[]=60a9a6f2ded39a0669ebc364&id[]=60a9a6f2ded39a0669ebc365&id[]=60a9a6f2ded39a0669ebc366&id[]=60a9a6f2ded39a0669ebc367&id[]=60a9a6f2ded39a0669ebc368&id[]=60a9a6f2ded39a0669ebc369&token=2c0cd1ba3be04541a86e66647f0f8d93&serverKey=15F3D81293D89A59B4D213FD44C5100FC215EBFF]. 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 [/omada/3.2.3/hotspot/static/printVoucher.html?type=include&id[]=60006793ded39a066906e793&id[]=60006793ded39a066906e7b0&id[]=60006793ded39a066906e7b3&id[]=60a9a6f2ded39a0669ebc360&id[]=60a9a6f2ded39a0669ebc361&id[]=60a9a6f2ded39a0669ebc362&id[]=60a9a6f2ded39a0669ebc363&id[]=60a9a6f2ded39a0669ebc364&id[]=60a9a6f2ded39a0669ebc365&id[]=60a9a6f2ded39a0669ebc366&id[]=60a9a6f2ded39a0669ebc367&id[]=60a9a6f2ded39a0669ebc368&id[]=60a9a6f2ded39a0669ebc369&token=2c0cd1ba3be04541a86e66647f0f8d93&serverKey=15F3D81293D89A59B4D213FD44C5100FC215EBFF]. 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:888)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1597)
	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.

Apache Tomcat/9.0.41

 

For your immediate assistance please.

 

Thanks!

john.redcat wrote

Hi,

 

I encountered and error in OMADA controller OC200. I could not print created vouchers as I encountered an error when I am about to print them:

 

 

HTTP Status 400 – Bad Request

Type Exception Report

Message Invalid character found in the request target [/omada/3.2.3/hotspot/static/printVoucher.html?type=include&id[]=60006793ded39a066906e793&id[]=60006793ded39a066906e7b0&id[]=60006793ded39a066906e7b3&id[]=60a9a6f2ded39a0669ebc360&id[]=60a9a6f2ded39a0669ebc361&id[]=60a9a6f2ded39a0669ebc362&id[]=60a9a6f2ded39a0669ebc363&id[]=60a9a6f2ded39a0669ebc364&id[]=60a9a6f2ded39a0669ebc365&id[]=60a9a6f2ded39a0669ebc366&id[]=60a9a6f2ded39a0669ebc367&id[]=60a9a6f2ded39a0669ebc368&id[]=60a9a6f2ded39a0669ebc369&token=2c0cd1ba3be04541a86e66647f0f8d93&serverKey=15F3D81293D89A59B4D213FD44C5100FC215EBFF]. 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 [/omada/3.2.3/hotspot/static/printVoucher.html?type=include&id[]=60006793ded39a066906e793&id[]=60006793ded39a066906e7b0&id[]=60006793ded39a066906e7b3&id[]=60a9a6f2ded39a0669ebc360&id[]=60a9a6f2ded39a0669ebc361&id[]=60a9a6f2ded39a0669ebc362&id[]=60a9a6f2ded39a0669ebc363&id[]=60a9a6f2ded39a0669ebc364&id[]=60a9a6f2ded39a0669ebc365&id[]=60a9a6f2ded39a0669ebc366&id[]=60a9a6f2ded39a0669ebc367&id[]=60a9a6f2ded39a0669ebc368&id[]=60a9a6f2ded39a0669ebc369&token=2c0cd1ba3be04541a86e66647f0f8d93&serverKey=15F3D81293D89A59B4D213FD44C5100FC215EBFF]. 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:888)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1597)
	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.

Apache Tomcat/9.0.41

 

For your immediate assistance please.

 

Thanks!

 

  0  
  0  
#4
Options
Re:HTTP Status 400 – Bad Request
2021-06-01 12:40:39

Dear @marksyph, @john.redcat,

 

marksyph wrote

@john.redcat same issue here

 

To better assist you, please kindly provide the device information(model and firmware version), and tell how you access the hotspot manager to print vouchers. Thank you!

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#5
Options
Re:HTTP Status 400 – Bad Request
2021-06-01 15:19:15
Hi Sir, What's the current firmware version of your OC200, please?- oc200 no. 1-version 3.2.12; firmware 1.2.3 Build 20200430 Rel.52621; oc200 no. 2-version 3.2.14 firmware 1.2.4 Build 20201120 Rel.51842;3.2.3 Did you access the Hotspot manager to print vouchers via cloud access (by visiting https://omada.tplinkcloud.com/)?-Yes
  0  
  0  
#6
Options
Re:HTTP Status 400 – Bad Request
2021-06-01 15:20:26
Hi Sir, What's the current firmware version of your OC200, please?- oc200 no. 1-version 3.2.12; firmware 1.2.3 Build 20200430 Rel.52621; oc200 no. 2-version 3.2.14 firmware 1.2.4 Build 20201120 Rel.51842;3.2.3 Did you access the Hotspot manager to print vouchers via cloud access (by visiting https://omada.tplinkcloud.com/)?-Yes
  0  
  0  
#7
Options
Re:HTTP Status 400 – Bad Request
2021-06-02 00:35:41
OMADA Model:OC200 1.0 Firmware Version:1.2.3 Build 20200430 Rel.52621 Controller Version:3.2.12 I am printing via cloud via the voucher manager for portal access authentication
  0  
  0  
#8
Options
Re:HTTP Status 400 – Bad Request
2021-06-02 00:35:59
OMADA Model:OC200 1.0 Firmware Version:1.2.3 Build 20200430 Rel.52621 Controller Version:3.2.12 I am printing via cloud via the voucher manager for portal access authentication
  0  
  0  
#9
Options
Re:HTTP Status 400 – Bad Request
2021-06-03 07:21:54
Yes is it ok for print unused voucher, but when I print through selective printing, that error occurs
  0  
  0  
#10
Options
Re:HTTP Status 400 – Bad Request-Solution
2021-06-03 07:35:21 - last edited 2021-06-04 03:20:27

Dear @john.redcat,

 

john.redcat wrote

Yes is it ok for print unused voucher, but when I print through selective printing, that error occurs

 

Thank you for your valued feedback. I've reported the issue to the R&D team for further investigation.

 

Update: The issue has been fixed now. Please confirm it.

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#11
Options

Information

Helpful: 0

Views: 2172

Replies: 11

Related Articles