02:08
<gsnedders>
annevk: I'm trying!
08:33
<annevk>
Domenic: do you also report the users that file bogus issues?
08:33
<annevk>
Domenic: I usually just report them and pass the link along to GitHub, they then remove the issue altogether
10:52
<nox>
annevk, TabAtkins: Selection is kinda broken in the DOM spec.
10:53
<nox>
Ah no, never mind, it's Safari that is broken.
10:53
<nox>
https://dom.spec.whatwg.org/#dom-nondocumenttypechildnode-nextelementsibling Triple clicking on that sentence somehow doesn't select it anymore.
13:28
<Domenic>
annevk: yep, reported
15:09
<annevk>
Great
15:10
<annevk>
I guess I might close them too going forward for signaling purposes
19:12
<dekiss>
where can I read the most recent http specification?
19:21
<dekiss>
I guess this is newwest? http://www.ietf.org/rfc/rfc2616.txt
20:46
<Domenic>
dekiss: see https://fetch.spec.whatwg.org/#references [HTTP]; it's a collection of new RFCs
22:39
<dekiss>
I am sending custom http request to my apache web server and I am pretty much sure the http request is well formed it has only http request header but in my apache logs there is the reqeust with code 400 which means it was bad request, why is that?
22:40
<dekiss>
I made custom web server and made request opening localhost with chrome browser and I copied the request that chrome sent to my server to make custom http requestto apache that is on my same machine, I am sending the custom reqeust with the web client that I made in c++