Search results

Hi Rudi, Thanks for reporting. I've added it to our bug list. I'm not sure that this is the most high priority issue, but we will get to it. Cheers, Michael

Hi Luis, If you're asking about how HTTP/2 support is doing right now, there are some bugs still, but we're working on improving it. It does support curl. We are working on getting it in line with the h2spec test right now. Cheers, Michael

Hmmm... That is weird. We're doing a lot of work on HTTP/2 right now, so maybe it will be fixed in the next release. (Or maybe in Chrome's next release.) It will be very hard to fix it before we can isolate what part is causing the issue, though.

See, to me, that sounds like a lot of maintenance left to be done. But I don't even change my own oil. (And I have no idea what an FJR is...) m

I'm sorry to hear that. Have you narrowed down what might be causing it. That's quite a few variables you have there. Michael

Howdy all, We just put out versions 1.3.9 and 1.4.6. They contain numerous bug fixes and improvements to our HTTP/2 support. The most important fix is probably for a high CPU usage problem that a couple users reported. Anyone on 1.3.8 or 1.4.5 should definitely upgrade to the next version...

Rewrite problem perhaps? Did you copy and paste Apache rewrites? m

Really? That seems like a monumental project... No?

Hey Tracy, So the conversation kind of stalled a little while back. Have you had a chance to try any of the installs since 1.4.4? m

Howdy @Rudi, I just wanted to let you know that the developers have looked at this. They think the issue may have been caused by using an IPv6 address with -b. Have you tried this with an IPv4 address. (I know you fixed it, but, well, I'd like to know.) Cheers, Michael

Howdy, Sorry for not replying. Somehow I missed this. There should not be. If you upgrade from 1.3.x to 1.4.x your configs will be automatically updated to plain text configs (from XML). If you see any loss of configs, please let us know. That would be a bug. Michael

Right. So you want to expose it to more SAPIs? That's cool, but I can't help but ask why? What would you be hoping to connect it to? Still, if you want to do it, I'd like to see if someone can help you. Let me see what people say. m

Hi, Thanks for your interest in OpenLiteSpeed. I was talking with the developers about this thread during lunch. It's probably best not to build any modules for LSIAPI yet, since it's still in flux. Also, we're not quite sure what you're trying to do. It seems like the module you're...

Howdy @tyteen4a03 Sorry if this is confusing. I believe these may be holdovers from Enterprise settings. I'm not quite sure what they do on OpenLiteSpeed. For setting up suEXEC, though, you need to set the VHost Security > ExtApp Set UID Mode setting. This should enable suEXEC for this vhost...

Hi @isengard I'm not sure exactly what is causing this bug, but we have found that there is a bug in 1.3.8 that is causing high load. The bug does not exist in 1.3.7, so you can downgrade one version if you like. We also should be releasing a fix for this bug soon. The developers say they have...

Luis, Your English is perfectly fine. It is far better than my Portuguese. (I'm guessing you're Brazilian? Sorry if I'm mistaken.) Cheers, Michael

Hmmm... I don't know why I didn't get the alert about this post earlier. @Luis Pavaneli also sent me a PM and I got that right away. Well, here's what I told him via PM: It looks like there's a bug with 1.3.8 that's causing high load. We're working on solving it now, but, until it's solved, it...

Hi @fireup6, Server push is something we'll be looking at in the future, but it's not something we're working on right now. Right now we're working to shore a lot of our internal functions and make sure the current HTTP/2 support is solid.Thanks for letting us know that it's important to you...

Hi @getphuture, You mean that our wiki is missing the steps you need to take in the Virtual Host configs under the SSL tab, right? Thanks for pointing that out! m

Alright. Thanks for confirming! Apparently, this wasn't fixed after all. I'm starting a new bug report: https://github.com/litespeedtech/openlitespeed/issues/25 By the way, anyone who's reading this can file bug reports on Github any time they want. m