lighty labs

2010-07-05

08:41 Lighttpd Bug #2221: responceText incorrect on 403

>> There is no standard conforming way of delivering .svgz, as not all http clients have to support compression.
>>
... lightning

2010-07-04

15:50 Lighttpd Bug #2221 (Reopened): responceText incorrect on 403

I agree setenv.add-response-header is bad, I already said it was a hack and I am looking for correct, clean solution.... lightning

2010-06-08

21:02 Lighttpd Bug #2221: responceText incorrect on 403

Maybe what? Maybe bad usage or maybe setenv.add-response-header is unsafe?
mimetype.assign = (
".sv... lightning

2010-06-07

20:12 Lighttpd Bug #2221: responceText incorrect on 403

FYI:
http://www.w3.org/TR/2008/WD-SVGMobile12-20080912/conform.html#ConformingSVGServers
the encoding header seem... lightning

11:02 Lighttpd Bug #2221: responceText incorrect on 403

In fact this sort of regex matching on the URL is nothing better that file extension sniffing. Is there a way to set ... lightning

09:40 Lighttpd Bug #2221: responceText incorrect on 403

Feature requests aside , you can't send out a header that announces compressed data then send text in rest of the pac... lightning

2010-06-06

20:49 Lighttpd Bug #2221 (Reopened): responceText incorrect on 403

Hmm, maybe there is a bug here.
Here's firefox requesting the svgz when evasive.max-conns-per-ip = 3 . This rapidly ... lightning

18:26 Lighttpd Bug #2221: responceText incorrect on 403

>> What content-type header was sent?
either it was in response to :
function refresh_svg(){ ... lightning

16:24 Lighttpd Bug #2221: responceText incorrect on 403

OK, it looks like lighttpd's output was correct. It was firefox perverting it.
FF had the good idea to insert the... lightning

11:37 Lighttpd Bug #2221: responceText incorrect on 403

What happened to the edit facility?
v 1.4.26 lightning