revious 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.
>
>
r
learning/tinkering?
Thanks!
--
Simon Roberts
(303) 249 3613
d the
problem when it was sending the wrong line-endings.
Anyway, hopefully you can look at the protocol exchange and see what node
is doing that's wrong.
If you need any updates to the node server, just holler, I'll be around and
able to put a few minutes into this here a
tand exactly what the
> problem is here. I can try out node.js myself, or if anyone
> has some instructions to help set that up it would be
> helpful.
>
> -Chris.
--
Simon Roberts
(303) 249 3613
> 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
(new OutputStreamWriter(s.getOutputStream()));
for (var st : response) {
out.print(st + "\r\n");
System.out.println("> " + st);
}
out.flush();
s.close();
}
}
On Tue, May 15, 2018 at 1:55 PM Simon Roberts <
si...@dancingcloudservices.com> wrote:
>
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
reamWriter(s.getOutputStream()));
for (var st : response) {
out.print(st + "0x000D0x000A");
System.out.println("> " + st);
}
out.flush();
s.close();
On Tue, May 15, 2018 at 12:44 PM Simon Roberts <
si...@dancingcloudservices.com> wrote:
>
dows)ö
>
> Gruss
> Bernd
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> --
> *From:* net-dev on behalf of Simon
> Roberts
> *Sent:* Tuesday, May 15, 2018 7:22:27 PM
> *To:* net-dev@openjdk.java.net
> *Subject:* EOF excption
tWriter(new OutputStreamWriter(s.getOutputStream()));
for (var st : response) {
out.println(st);
System.out.println("> " + st);
}
out.flush();
s.close();
}
}
On Tue, May 15, 2018 at 9:46 AM Chris Hegarty
wrote:
> Simon,
>
> Only a partial reply, I’ll r
ient/jdk.incubator.http.HttpClientImpl$SelectorManager.handleEvent(HttpClientImpl.java:769)
at
jdk.incubator.httpclient/jdk.incubator.http.HttpClientImpl$SelectorManager.run(HttpClientImpl.java:731)
Process finished with exit code 0
On Tue, May 15, 2018 at 8:38 AM Chris Hegarty
wrote:
> Simon,
>
> >
s it as an unrecoverable failure.
On Tue, May 15, 2018 at 7:31 AM Chris Hegarty
wrote:
> Simon,
>
> > On 15 May 2018, at 14:25, Simon Roberts
> wrote:
> >
> > ...
> > I'm running on Linux, not Mac, and t's just a thrown together node.js
> ser
sed server instead.
On Tue, May 15, 2018 at 7:25 AM Simon Roberts <
si...@dancingcloudservices.com> wrote:
> Daniel: Thanks, it did seem improbable, but seemed to be the only common
> factor. But I suspect Joakim's astute observation is more relevant.
>
> I'm running on
erver is reporting the wrong Content-Length.
>
> "HeadingSome Text" is 59
> characters
>
> But the server said "Content-Length: 58"
>
> Also, "Connection: keep-alive" is a HTTP/1.0 concept only, but is being
> reported on your HTTP/1.1 reques
I have a very simple attempt to use the Java 10 / incubator httpclient api.
It works on "regular" resources, but fails horribly when attempting to get
things from localhost. It fails using 127.0.0.1, the actual non-loopback
IP, and the name localhost. The server is running, and presenting a very
si
15 matches
Mail list logo
