Latest activity

Congratulations! Sue LiteSpeed for violating the RFC! ;)

No, it's not my personal logic. It's RFC. Quoted from RFC: "SHOULD process the response as if it had a 5xx" means it HAS to be logged...

That's a given, but don't try to apply your "personal logic" to how something should work.

You clearly didn't understand anything of what I'm doing. I said I already know how to recognize the ones I need to, because we are...

I appreciate your efforts to block scrapers and other unwanted requests. However, be aware that this isn't possible with conventional...

Yeah I know. Anyway the RFC you quoted should be applied regardless of the version. So it applies to both. Even OLS replies correctly...

LSE = LSWS (LiteSpeed Enterprise Web Server) also follows RFC, but you should use LSWS support for related questions or issue. The...

I forgot to say I use LSE not OLS. I expect a correct logging nonetheless. No matter what response code is there. Logging should not...

OLS is not Apache. If OLS doesn't use status code 500 if a status code outside the valid range is used this is just an undefined case in...

I see, I read in RFC 2616 it says: I supposed it would work. Well I'll just use 418. Anyway logging, even an unknown response, should...

Any status code smaller 100 and higher 599 is invalid. Using status codes outside this range causes error 500, so this is not a OLS bug...

I use mod_security to return a custom error code 6xx on some requests, so I can later work them with crowdsec actions. However any...

Hey, thanks for such a litespeed replies as well as asked i have mailed GDB backtrace ✅ Core file analysis ✅ Thank you Team

Hey, thanks for such a litespeed replies as well as asked i have mailed GDB backtrace ✅ Core file analysis ✅ Thank you Team

Thanks for the report, will check it further via the support ticket.