I finally found the point.
If using directory xxx.war, Jetty would throw
java.lang.IllegalStateException like the below:
No LoginService for
org.eclipse.jetty.security.authentication.BasicAuthenticator@24a35978 in
org.eclipse.jetty.security.ConstraintSecurityHandler@16f7c8c1
If using archive
Any update ;-)
2016-09-08 5:51 GMT+08:00 John Jiang :
> Hi,
> BTW, I suffered from another problem when migrated my base to the new
> built Jetty.
>
> My application setups a Basic Authentication, like the below,
> web.xml
>
> BASIC
> Test Realm
>
>
>
>
2016-09-08 18:40 GMT+08:00 Simone Bordet :
> Hi,
>
> On Thu, Sep 8, 2016 at 11:24 AM, John Jiang
> wrote:
> > I suppose Apache doesn't reset it. The stream just closes with NO_ERROR
>
> What client is this, curl ?
>
Yes.
>
> Note that the stream
Hi,
2016-09-08 15:27 GMT+08:00 Simone Bordet :
> Hi,
>
> On Thu, Sep 8, 2016 at 1:25 AM, John Jiang
> wrote:
> > Tested the same cases with Apache 2.4.17, but no such message found.
> > It looks Apache uses NO_ERROR.
>
> Apache resets the stream
Hi,
On Thu, Sep 8, 2016 at 1:25 AM, John Jiang wrote:
> Tested the same cases with Apache 2.4.17, but no such message found.
> It looks Apache uses NO_ERROR.
Apache resets the stream with NO_ERROR ?
The reset is fine, using NO_ERROR seems misleading, since the server
2016-09-07 16:39 GMT+08:00 Simone Bordet :
> Hi,
>
> On Wed, Sep 7, 2016 at 7:56 AM, John Jiang
> wrote:
> > But I still found something interesting.
> > In my webapp, /body is a pretty simple Servlet, which just print
> something.
>
> Your servlet
Java Environment:
-
java.home = C:\Programs\Java\jdk1.8.0\jre
java.vm.vendor = Oracle Corporation
java.vm.version = 25.60-b23
java.vm.name = Java HotSpot(TM) 64-Bit Server VM
java.vm.info = mixed mode
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version =
Run this and report back ...
$ cd /path/to/mybase
$ java -jar /path/to/jetty-dist/start.jar --list-config
Joakim Erdfelt / joa...@webtide.com
On Wed, Sep 7, 2016 at 2:51 PM, John Jiang wrote:
> Hi,
> BTW, I suffered from another problem when migrated my base to the
Hi,
BTW, I suffered from another problem when migrated my base to the new built
Jetty.
My application setups a Basic Authentication, like the below,
web.xml
BASIC
Test Realm
Authentication
/auth/*
admin
user
moderator
mybase/etc/test-realm.xml
Hi,
On Wed, Sep 7, 2016 at 7:56 AM, John Jiang wrote:
> But I still found something interesting.
> In my webapp, /body is a pretty simple Servlet, which just print something.
Your servlet does one important thing: it calls
request.getInputStream(), which triggers the
Hi,
On Tue, Sep 6, 2016 at 2:24 PM, John Jiang wrote:
> Hi Simone,
>
> 2016-09-06 18:03 GMT+08:00 Simone Bordet :
>>
>> Hi,
>>
>> On Tue, Sep 6, 2016 at 12:00 PM, Simone Bordet
>> wrote:
>> > It was a bug, tracked here:
>> >
Hi Simone,
2016-09-06 18:03 GMT+08:00 Simone Bordet :
> Hi,
>
> On Tue, Sep 6, 2016 at 12:00 PM, Simone Bordet
> wrote:
> > It was a bug, tracked here: https://github.com/eclipse/
> jetty.project/issues/902
>
> It's fixed, can you try the latest Jetty
Hi,
On Tue, Sep 6, 2016 at 12:00 PM, Simone Bordet wrote:
> It was a bug, tracked here:
> https://github.com/eclipse/jetty.project/issues/902
It's fixed, can you try the latest Jetty 9.3.x code and report back if
it's working for you ?
--
Simone Bordet
Hi,
On Tue, Sep 6, 2016 at 7:37 AM, John Jiang wrote:
> I'm using Jetty 9.3.8, and made it supporting h2 and h2c, like the below
> info on starting the server.
> 2016-09-06 13:23:52.505:INFO:oejs.ServerConnector:main: Started
>
I'm using Jetty 9.3.8, and made it supporting h2 and h2c, like the below
info on starting the server.
2016-09-06 13:23:52.505:INFO:oejs.ServerConnector:main: Started
ServerConnector@1f021e6c{HTTP/1.1,[http/1.1, h2c, h2c-17, h2c-16, h2c-15,
h2c-14]}{0.0.0.0:9020}
...
2016-09-06
15 matches
Mail list logo