On 11/12/17 19:12, Chris Cheshire wrote:
> I thought more about this over the weekend, and realised it is more
> hassle than it is worth, and not because I don't want to do it. I
> don't think it is actually feasible now that I think about it more.
>
> Given that a JVM has one set of System.proper
I thought more about this over the weekend, and realised it is more
hassle than it is worth, and not because I don't want to do it. I
don't think it is actually feasible now that I think about it more.
Given that a JVM has one set of System.properties and one instance of
Tomcat can have multiple d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 12/10/17 3:11 PM, Mark Thomas wrote:
> On 09/12/17 19:41, Christopher Schultz wrote:
>
>
>
>> If there is any appetite for such a thing in Tomcat, I'd be happy
>> to propose a change to bring e.g. an AuthenticationListener
>> interface w
On 11 December 2017 14:34:01 GMT+00:00, "Lueders, Paul T CIV USARMY NGIC (US)"
wrote:
>CLASSIFICATION: UNCLASSIFIED
>
>I am running Apache tomcat 7.0.82. It is not running behind any other
>web server. I am getting:
>Java.lang.IllegalArgumentException: Invalid Character found in the
>request ta
On Mon, Dec 11, 2017 at 9:34 AM, Lueders, Paul T CIV USARMY NGIC (US)
wrote:
> CLASSIFICATION: UNCLASSIFIED
>
> I am running Apache tomcat 7.0.82. It is not running behind any other web
> server. I am getting:
> Java.lang.IllegalArgumentException: Invalid Character found in the request
> targe
CLASSIFICATION: UNCLASSIFIED
I am running Apache tomcat 7.0.82. It is not running behind any other web
server. I am getting:
Java.lang.IllegalArgumentException: Invalid Character found in the request
target. The valid characters are defined in RFC 7230 and RFC 3986
How can I correct this in
