java.lang.IllegalArgumentException

Invalid character found in method name. HTTP method names must be tokens


Samebug tips3

You might send a large amount of data in the request URL. Consider sending it in the request body.

This error is caused by malformed HTTP request. You are trying to access unsecured page through https.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.


Solutions on the web19998

Solution icon of googlegroups
via Google Groups by Xin Gong, 10 months ago
Invalid character found in method name. HTTP method names must be tokens

Solution icon of web
Invalid character found in method name. HTTP method names must be tokens

Solution icon of github
via GitHub by vbootstrap
, 3 days ago
Invalid character found in method name. HTTP method names must be tokens

Solution icon of googlegroups
via Google Groups by Robert van der Spek, 4 months ago
Invalid character found in method name. HTTP method names must be tokens

Solution icon of stackoverflow
Invalid character found in method name. HTTP method names must be tokens

Solution icon of stackoverflow
Invalid character found in method name. HTTP method names must be tokens

Solution icon of stackoverflow
via Stack Overflow by Bala Murugan
, 7 months ago
Invalid character found in method name. HTTP method names must be tokens

Solution icon of stackoverflow
via Stack Overflow by sri
, 6 months ago
Invalid character found in method name. HTTP method names must be tokens

Solution icon of stackoverflow
Invalid character found in method name. HTTP method names must be tokens

Solution icon of stackoverflow
via Stack Overflow by KJEjava48
, 2 months ago
Invalid character found in method name. HTTP method names must be tokens

Stack trace

  • java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1524) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1480) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Unknown Source)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 11 months ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
29 more bugmates