HTTP Status 400 – Bad Request


Type Exception Report

Message Request header is too large

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: Request header is too large
	org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:778)
	org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:892)
	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:593)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:279)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:937)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)
	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
	java.base/java.lang.Thread.run(Unknown Source)

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


Apache Tomcat/9.0.96

Menu Search

Quarter Turn T Handle

In stock

Cam Latches with compression have a T-shaped handle. They are designed to offer secure access to panels and doors, courtesy of the rotating cam (pawl).

The cam is secured by engaging the frame or keeper on the back side. These latches come with standard technology. Ideally used for cabinets that require better sealing under vibration conditions.

  • Cam Material: Stainless Steel
  • Latch Material: Nylon 6/6
  • Colour: Black
  • DIN-EN 1774 rated

Cam sold separately

Request a quote

For large volumes and customized products, add to your cart and click request a quote orcontact usand we will respond in 24 hours or next business day

Filter or Search Variants

Use the filters or search below to find what you're looking for

Imperial
Metric
Hide Show Filters
1 result
Product SKUs information
Item Code Price range Availability Handle Length Housing Height Head Height View
$19.60 - $22.50 227 In stock
2.913 in
0.728 in
Quarter Turn T Handle - ; Key Type: Key Operated

110200700

Price Range
$22.50 - $19.60

Stock Levels
227 In stock
Attributes
  • Handle Length
    2.913 in
  • Housing Height
    0.728 in
  • Colour
    Black
  • Includes
    Cam Sold Separately. Two keys supplied with each latch
  • Key Type
    Key Operated
HTTP Status 400 – Bad Request

HTTP Status 400 – Bad Request


Type Exception Report

Message Request header is too large

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: Request header is too large
	org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:778)
	org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:946)
	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:593)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:279)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:937)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)
	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
	java.base/java.lang.Thread.run(Unknown Source)

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


Apache Tomcat/9.0.96

HTTP Status 400 – Bad Request

HTTP Status 400 – Bad Request


Type Exception Report

Message Request header is too large

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: Request header is too large
	org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:778)
	org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:892)
	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:593)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:279)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:937)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)
	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
	java.base/java.lang.Thread.run(Unknown Source)

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


Apache Tomcat/9.0.96

HTTP Status 400 – Bad Request

HTTP Status 400 – Bad Request


Type Exception Report

Message Request header is too large

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: Request header is too large
	org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:778)
	org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:972)
	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:593)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:279)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:937)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)
	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
	java.base/java.lang.Thread.run(Unknown Source)

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


Apache Tomcat/9.0.96