Hi Simone,
Thanks for your help!
BTW, why org.eclipse.jetty.servlets.PushCacheFilter can use
org.eclipse.jetty.server.Request directly?
2015-12-31 18:32 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Wed, Dec 30, 2015 at 1:03 PM, John Jiang <john.sha.ji...@
gt; On 30 Dec 2015 14:04, "John Jiang" <john.sha.ji...@gmail.com> wrote:
>
>> Hi guys,
>> I'm using Jetty-9.3.5.
>> My web app includes a pretty simple Servlet, as shown as the below,
>> public class ServerPushServlet extends HttpServle
Hi guys,
I'm using Jetty-9.3.5.
My web app includes a pretty simple Servlet, as shown as the below,
public class ServerPushServlet extends HttpServlet {
protected void doGet(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
IOException {
Hi Simone,
2016-02-07 18:43 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Fri, Feb 5, 2016 at 6:30 AM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
> > Hi guys,
> > It seems that Jetty HTTP/2 server cannot
figure any more?
Thanks!
>
> --
> jesse mcconnell
> jesse.mcconn...@gmail.com
>
> On Thu, Feb 4, 2016 at 11:30 PM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
>
>> Hi guys,
>> It seems that Jetty HTTP/2 server cannot be connected via its HTTP/1
>
Hi guys,
It seems that Jetty HTTP/2 server cannot be connected via its HTTP/1 client
(org.eclipse.jetty.client.HttpClient).
The error likes: Illegal character 0x0 in state=START for buffer...
But the HTTP/1 client can access Apache HTTP/2 server.
Is there any way to resolve/workaround this
TP, namely using url = "http://localhost:8080;, the
output is 200, which is normal.
2016-02-11 16:26 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Mon, Feb 8, 2016 at 1:41 PM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
> > Hi Simone,
>
Hi,
I setup a jetty-alpn.xml, and set the default protocol for
ALPNServerConnectionFactory.
Now, it works.
Thanks!
2016-03-31 17:01 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Thu, Mar 31, 2016 at 10:44 AM, John Jiang <john.sha.ji...@gmail.com>
>
de with request body is
illegal.
Thanks!
2016-05-01 23:48 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Sun, May 1, 2016 at 5:36 PM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
> > Hi,
> > I'm using standalone Jetty 9.3.8.
> > It looks that the p
Hi,
I'm using standalone Jetty 9.3.8.
It looks that the plaintext HTTP/2 doesn't support request body.
If a request includes body, the upgrade will fail.
Thanks!
___
jetty-users mailing list
jetty-users@eclipse.org
To change your delivery options,
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
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,
2016-09-08 15:27 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Thu, Sep 8, 2016 at 1:25 AM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
> > Tested the same cases with Apache 2.4.17, but no such message found.
> > It looks Apache uses NO
art(ScopedHandler.java:120)
Does Jetty make some change on this area?
Or I missed something on the migration?
2016-09-06 21:00 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Tue, Sep 6, 2016 at 2:24 PM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
> > Hi
2016-09-07 16:39 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Wed, Sep 7, 2016 at 7:56 AM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
> > But I still found something interesting.
> > In my webapp, /body is a pretty simple Servlet, which just
Joakim Erdfelt / joa...@webtide.com
>
> On Wed, Sep 7, 2016 at 2:51 PM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
>
>> Hi,
>> BTW, I suffered from another problem when migrated my base to the new
>> built Jetty.
>>
>> My application
Any update ;-)
2016-09-08 5:51 GMT+08:00 John Jiang <john.sha.ji...@gmail.com>:
> 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
2016-09-08 18:40 GMT+08:00 Simone Bordet <sbor...@webtide.com>:
> Hi,
>
> On Thu, Sep 8, 2016 at 11:24 AM, John Jiang <john.sha.ji...@gmail.com>
> wrote:
> > I suppose Apache doesn't reset it. The stream just closes with NO_ERROR
>
> What client is this, curl
file xxx.war, it's fine.
2016-09-09 2:47 GMT+08:00 John Jiang <john.sha.ji...@gmail.com>:
> Any update ;-)
>
> 2016-09-08 5:51 GMT+08:00 John Jiang <john.sha.ji...@gmail.com>:
>
>> Hi,
>> BTW, I suffered from another problem when migrated my base to the new
On Thu, Sep 12, 2019 at 3:41 AM Simone Bordet wrote:
> Hi,
>
> On Wed, Sep 11, 2019 at 4:35 AM John Jiang
> wrote:
> > Yes, curl tool doesn't support server push yet, even though libcurl
> supports that.
> > But as I mentioned in my last reply, this failure may not
On Wed, Sep 11, 2019 at 11:49 PM Joakim Erdfelt wrote:
> > jetty-http-9.4.20.v20190813.jar
> > jetty-io-9.4.20.v20190813.jar
> > jetty-server-9.4.20.v20190813.jar
> > jetty-util-9.4.20.v20190813.jar
>
> Remove the jetty-server jar at least.
> Those other 3 have no purpose on their own.
>
Then
> They fixed the bugs first in JDK12 and then backported to JDK11.
>
> On 9/12/19 10:15 AM, John Jiang wrote:
>
> On Thu, Sep 12, 2019 at 4:00 PM Simone Bordet wrote:
>
>> Hi,
>>
>> On Thu, Sep 12, 2019 at 12:55 AM John Jiang
>> wrote:
>> > Some of Jet
On Thu, Sep 12, 2019 at 4:00 PM Simone Bordet wrote:
> Hi,
>
> On Thu, Sep 12, 2019 at 12:55 AM John Jiang
> wrote:
> > Some of Jetty built-in servlets/filters, e.g PushCacheFilter, in
> jetty-servlets jar also call Request.getBaseRequest(request), and h
On Tue, Sep 10, 2019 at 7:50 PM Simone Bordet wrote:
> Hi,
>
> On Tue, Sep 10, 2019 at 1:41 PM John Jiang
> wrote:
> >
> > I wanted to test the HTTP/2 feature server push with Jetty 9.4.20, and
> made a simple servlet like the below,
> >
> > public clas
I wanted to test the HTTP/2 feature server push with Jetty 9.4.20, and made
a simple servlet like the below,
public class ServerPushServlet extends HttpServlet {
protected void doGet(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
IOException {
On Tue, Sep 10, 2019 at 11:32 PM Simone Bordet wrote:
> Hi,
>
> On Tue, Sep 10, 2019 at 2:05 PM John Jiang
> wrote:
> > I would have tried that with curl, like the below,
> > $ curl -v --http2 http://localhost:9020/push
> > * Trying ::1:9020...
> &g
On Wed, Sep 11, 2019 at 6:57 PM Joakim Erdfelt wrote:
> Can you change your implementation a bit so that we can understand what's
> going on?
>
> (the below code can be found at
> https://gist.github.com/joakime/ca3bf453cd946e47a8a09181ef3a0dd7 as well,
> and might be slightly more up to date)
>
Hi,
I'm using Jetty 10.0.0-alpha0
Please consider this case:
1. Client sends request for the below url,
http://host:port/push?query
2. Server pushes some resources, including img1, img2.
The push requests look like the followings,
http://host:port/img1?query
http://host:port/img2?query
Does it
intended by the spec.
>>
>> On Tue, 17 Sep 2019 at 01:58, Simone Bordet wrote:
>>
>>> Hi,
>>>
>>> On Mon, Sep 16, 2019 at 5:26 PM John Jiang
>>> wrote:
>>> >
>>> > Hi,
>>> > I'm using Jetty 10.0.0-alpha0
>&
Hi,
It looks Jetty server misses client cookie properties, like $Path, $Domain.
Please consider the below simple Servlet,
public class TestServlet extends HttpServlet {
protected void doGet(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
On Wed, Sep 11, 2019 at 9:46 PM Joakim Erdfelt wrote:
> HttpServletRequest is implemented by org.eclipse.jetty.server.Request
>> HttpServletRequest is instanceof Request = false
>
>
> What jetty jars do you have in your WEB-INF/lib ?
>
jetty-http-9.4.20.v20190813.jar
Anyway, I just filed issue:
https://github.com/eclipse/jetty.project/issues/4102
On Wed, Sep 18, 2019 at 4:28 PM John Jiang wrote:
> Hi,
> It looks Jetty server misses client cookie properties, like $Path, $Domain.
>
> Please consider the below simple Servlet,
> public class Test
Anyway, just filed https://github.com/eclipse/jetty.project/issues/4305
On Tue, Nov 12, 2019 at 2:48 PM John Jiang wrote:
> Hi,
> Using 9.4.22.
>
> My jetty server supports HTTP/2, including h2c and h2, and try the below
> command,
> openssl s_client -alpn h3,h4
Hi,
Using 9.4.22.
My jetty server supports HTTP/2, including h2c and h2, and try the below
command,
openssl s_client -alpn h3,h4 -connect host:port
For this case, per RFC 7301 section 3.2, the server shall alter fatal
no_application_protocol.
But with my testing, the server raised warning
Hi,
I'm using Jetty 10.0.0 alpha1.
With my testing, it looks TLSv1 and TLSv1.1 are disabled in this version.
I used OpenSSL s_client to connect the Jetty server via TLS.
If specified TLSv1.2 or TLSv1.3, the handshaking finished successfully.
However, when TLSv1 or TLSv1.1 were specified, the
Feb 6, 2020 at 1:47 PM John Jiang wrote:
> Hi,
> I'm using Jetty 10.0.0 alpha1.
>
> With my testing, it looks TLSv1 and TLSv1.1 are disabled in this version.
> I used OpenSSL s_client to connect the Jetty server via TLS.
> If specified TLSv1.2 or TLSv1.3, the handshaking
.*
TLS_ECDHE.*
TLS_AES.*
TLS_ECDH_.*
On Thu, Feb 6, 2020 at 3:46 PM John Jiang wrote:
> I just added file /etc/tweak-ssl.xml to enable all the TLS
> versions, like the below,
>"http://www.eclipse.org/jetty/con
37 matches
Mail list logo