Sending https traffic to an http endpoint might explain the unexpected
binary data like 0x03.
Andy
On 17/11/17 23:57, Marco Neumann wrote:
so I did a quick test with a fresh build and it's recurring via https
access requests on jetty. I think we can close this issue here in the
AJF3.6.0 thread.
On Fri, Nov 17, 2017 at 11:57 PM, Marco Neumann <[email protected]> wrote:
did an update yesterday. I will dig into this over the weekend.
On Fri, Nov 17, 2017 at 6:53 PM, Andy Seaborne <[email protected]> wrote:
On 17/11/17 15:59, Marco Neumann wrote:
just switched to AJF3.6.0 (TDB) . It's the first time I see this.
the index + spatial is older and was created with AJF3.4.0 (TDB)
I will do an update and see if that makes a difference
On Fri, Nov 17, 2017 at 4:53 PM, ajs6f <[email protected]> wrote:
0x3 is Ctrl-C. Does this happen repeatedly? Can you cause it to happen?
How is the request to Fuseki being generated?
ajs6f
On Nov 17, 2017, at 10:48 AM, Marco Neumann <[email protected]>
wrote:
this was (with some delay) followed by a
?query=ASK%0AWHERE%0A++%7B+%3Fs+%3Fp+%3Fo%7D%0A
no activity otherwise
[2017-11-17 10:28:36] Fuseki INFO [17] GET
http://www.lotico.com:3030/lotico/sparql?query=ASK%0AWHERE%0A++%7B+%3Fs+%3Fp+%3Fo%7D%0A
[2017-11-17 10:28:36] Fuseki INFO [17] GET /lotico :: 'sparql' ::
<none> ? query=ASK%0AWHERE%0A++%7B+%3Fs+%3Fp+%3Fo%7D%0A
[2017-11-17 10:28:36] Fuseki INFO 137.208.107.48 [17] Query M2 =
ASK WHERE { ?s ?p ?o}
[2017-11-17 10:28:36] Fuseki INFO [17] 200 OK (4 ms)
At this point, request [17] is finished. It has certainly finished with the
HTTP request.
1m30s later ...
[2017-11-17 10:30:22] HttpParser WARN Illegal character 0x3 in
state=START for buffer
HeapByteBuffer@6a797a1b[p=1,l=47,c=8192,r=46]={\x03<<<\x00\x00/*\xE0\x00\x00\x00\x00\x00Cookie:...nistr\r\n\x01\x00\x08\x00\x03\x00\x00\x00>>>6
GMT\r\nFuseki-Req...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
looks like another request coming in from the network before it gets near
Fuseki.
i.e. it's not related to the ASK above.
HttpParser is Jetty's code applied to bytes off the wire to make internal
objects.
Is it recurring?
Is this a v recent 3.6.0-SNAPSHOT? The Jetty version was upgraded in the
last week or so.
On Fri, Nov 17, 2017 at 4:38 PM, ajs6f <[email protected]> wrote:
Can you provide some more context please? How did you cause this? What
was the operation and the data?
ajs6f
On Nov 17, 2017, at 10:36 AM, Marco Neumann <[email protected]>
wrote:
does this looks familiar?
HttpParser WARN Illegal character 0x3 in state=START for buffer
HeapByteBuffer@6a797a1b[p=1,l=47,c=8192,r=46]={\x03<<<\x00\x00/*\xE0\x00\x00\x00\x00\x00Cookie:...nistr\r\n\x01\x00\x08\x00\x03\x00\x00\x00>>>6
GMT\r\nFuseki-Req...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
version: Apache Jena Fuseki 3.6.0-SNAPSHOT
--
---
Marco Neumann
KONA
--
---
Marco Neumann
KONA
--
---
Marco Neumann
KONA
