-
Type:
Improvement
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 9.10, 10.10, 11.1-SNAPSHOT
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Core, Nuxeo Drive
In NXDRIVE-1647, a mechanism at login time is implemented so that a link with HTTP as a protocol is also attempted using HTTPS as a protocol.
If the server is NOT configured to handle HTTPS protocol, on the server-side, at Drive connection time, the following happens in the server log:
sept. 24, 2019 10:55:07 AM org.apache.coyote.http11.Http11Processor service
INFOS: Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:426)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:687)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1459)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
This exception ought to be trapped and generate an explicit message ("WARN: It is unsafe to use Drive without HTTPS protocol") or this message ought not to appear at all.
- is caused by
-
NXDRIVE-1647 Check HTTPS when starting an engine
-
- Resolved
-
- is related to
-
-
- Resolved
-