Thanks for all of this Daniel. Yes I finally managed to build curl with
http2.0 support, and I see the same thing.
I hate when one wastes three days (and who knows what of all your time) on
a bug in a tool one was only using as ancillary support because one thought
it would be quick (though hopefu
Hi Simon,
In complement to my previous answer, please find some
additional info to your questions:
On 16/05/2018 17:24, Simon Roberts wrote:
Notes, as a result of the discussion, I deliberately added code, at line
56 of server.js, to try to ensure that it's sending \r\n.
You don't need to d
Hi Simon,
I have done some more investigation, and
I believe the issue here is that the `express` server
doesn't like the connection upgrade that our HTTP Client
asks for.
As a result instead of ignoring the upgrade and simply
replying with HTTP/1.1 the server seems to close the
connection just a
Your node server lies about its Content-Length.
That's the #1 reason for your issues, lack of truth about the
Content-Length.
When you under-send (Content-Length longer then actual response body
content), you get the java.io.EOFException: EOF reached while reading from
your initial message.
When
Hi Simon,
I don't want to speculate, but the line termination for headers
are supposed to be \r\n (CRLF) and the headers should be terminated
by a 'blank' line (containing only \r\n).
If the server isn't sending any CRLF, then the client might still
be trying to reach the end of the headers bloc
OK, here goes.
1) install node 8.11 from here: https://nodejs.org/
this should consist (though I could be wrong for mac or windows!) of
expanding the archive, and adding the contained 'bin' directory to your
path.
You should be able to execute the commands:
node --version
(note two minus-signs. Sh
Thanks for investigating this, Chris. I will put together a trivial node
server and instructions on how to set it up (it's delightfully simple)
Should be much less than an hour, if I can give it my un-distracted
attention...
On Wed, May 16, 2018 at 8:58 AM Chris Hegarty
wrote:
> Bernd,
>
> > On
Bernd,
> On 16 May 2018, at 00:43, Bernd Eckenfels wrote:
>
> ...
> For the httpclient code, the following improvements are IMHO possible:
>
> • As you mentioned the EOF should contain the callsite and not be
> transorted from a worker thread context. This can either be done by rethrwin
ush();
}
}
}
}
--
http://bernd.eckenfels.net
Von: Simon Roberts
Gesendet: Mittwoch, 16. Mai 2018 00:02
An: net-dev@openjdk.java.net
Betreff: Re: EOF excption in HTTP 1.1 server interaction
No, HTTP 2.0 is not supported by nodejs (... current LTS release,
eight-dot-some
> it’s 62 bytes.
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> --
> *From:* net-dev on behalf of Simon
> Roberts
> *Sent:* Tuesday, May 15, 2018 10:47:35 PM
> *To:* net-dev@openjdk.java.net
> *Subject:* Re: EOF excption in
t string without the EOLs.
Gruss
Bernd
--
http://bernd.eckenfels.net
From: net-dev
mailto:net-dev-boun...@openjdk.java.net>> on
behalf of Simon Roberts
mailto:si...@dancingcloudservices.com>>
Sent: Tuesday, May 15, 2018 8:44:08 PM
To: net-dev@openjdk.java
g without the EOLs.
>>
>> Gruss
>> Bernd
>> --
>> http://bernd.eckenfels.net
>> --
>> *From:* net-dev on behalf of Simon
>> Roberts
>> *Sent:* Tuesday, May 15, 2018 8:44:08 PM
>> *To:* net-dev@openjdk.java.ne
russ
> Bernd
> --
> http://bernd.eckenfels.net
> --
> *From:* net-dev on behalf of Simon
> Roberts
> *Sent:* Tuesday, May 15, 2018 8:44:08 PM
> *To:* net-dev@openjdk.java.net
> *Subject:* Re: EOF excption in HTTP 1.1 server interaction
>
> Th
I have further tweeked my "fake server" so that it should respond with CRLF
at line endings, and tried it with content lengths of 58, 59, and 60.
Regardless, the httpdlient fails *on the call to send* with each of these
experiments. Are there any additional tests or variations that people
suggest t
Thanks for the clarification; as I mentioned, I tried a number of
variations, with and without the "excess" empty lines. I also copied the
output from a curl session with a server that provides a successful
interaction with the client (so the content length etc were all correct).
In every case the
15 matches
Mail list logo
