[DGD] instant replies to HTTP requests confusing browser?

[Neil McBride]

I remember having similar problems when writing a web server to work 
with my kernel based library. There were times I was convinced Chrome 
was broken. I was using Websockets when they were new and only available 
in Chrome just to make it more annoying too. The only way I found to 
reliably solve the problem was to put insane amounts of logging in. This 
let me see the difference between what I thought I'd programmed to 
happen and what was actually happening. Just put the logging in so you 
can turn it on/off as you will likely need it again.

I can confirm that what I end up with was working well a couple of years 
ago and still works nicely with Chrome today. Even the websockets 
communication that allows for a telnet style interface written in 
javascript is still working properly. You're making me want to dig it 
out and do some more work on it ...

Have fun digging :)

Neil.

On 17/10/2015 5:50 AM, Raymond Jennings wrote:
> The site is shentino.mynetgear.com, http is port 50080
>
> My suspicious are a race condition of sorts that causes things to choke.
> Hammering it with telnet repeatedly reliably and prompty gets back the
> error page.
>
> If you can find out anything by testing I would be quite intrigued.
>
> On Fri, Oct 16, 2015 at 7:47 AM, Andrew Skalski <askalski at gmail.com> wrote:
>
>> I'd be interested to see this in action.  My IP is 68.133.31.149, so
>> if you siteban that and give me a URL to hit, I can see if I can
>> reproduce it either in Chromium or Chrome (Linux), then use tcpdump to
>> see what's going wrong.
>>
>> (Assuming you haven't figured it out already.)
>>
>> Andy Skalski
>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Thu, 15 Oct 2015 19:52:43 -0700
>>> From: Raymond Jennings <shentino at gmail.com>
>>> To: "All about Dworkin's Game Driver" <dgd at dworkin.nl>
>>> Subject: [DGD] instant replies to HTTP requests confusing browser?
>>> Message-ID:
>>> <CAGDaZ_rOUJrg3f+_MG9qao2+rHegxAiq-OLABwxLFv4BVPu4WQ at mail.gmail.com>
>>> Content-Type: text/plain; charset=UTF-8
>>>
>>> Taking a page out of skotos's book, I added an Http module to kotaka.
>>>
>>> I'm having some problems though after having my system userd check a
>>> connection's ip against the siteban manager before passing the connection
>>> to the http userd.
>>>
>>> If the IP is sitebanned, the system userd merely asks the http userd for
>> a
>>> siteban message and then returns that before closing the connection
>>> immediately without even waiting for a request.
>>>
>>> Sometimes the browser shows the error page, and sometimes shows nothing
>> at
>>> all.
>>>
>>> Is there any reason this is going on?  Is it buggy behavior in chrome or
>> am
>>> I violating HTTP/1.1 somehow?
>>>
>>>
>>> ------------------------------
> ____________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd