Litespeed vs Apache for WordPress

A lot of blog posts from the Litespeed company claiming that Apache is very bad for WordPress hosting.

What I know is Apache is free and popular since many years already, at least 20 years. So why Apache is suddenly "bad" after 2019 according to all of their blog posts? They said because of HTTP3

And other forums, confirm that HTTP3 is not supported in Firefox and Chrome and any devices yet.. so who cares?
https://webmasters.stackexchange.com/questions/21862/does-using-litespeed-instead-of-apache-speed-up-wordpress

you must pay for Litespeed server license, but Apache is still free. And if Litespeed kills Apache than every web hosting will be more expensive?.. seems suspicious.

Is Apache really dead? or they will support HTTP3 coming soon. What is the real story about all of this posting.

5 Replies

Is Apache really dead?

No… I'm absolutely confident about this. apache2 critics said the same thing about HTTP2. apache2 has been around longer than nginx and Litespeed combined…

Will apache2 change…most likely. Will apache2 disappear…maybe -- replaced by apache3apache2 has an installed base and ecosystem that Litespeed can only salivate over. apache2 works; it's stable; it's well-documented; and tons of people use it (incl yours truly). Litespeed probably only wishes half of that were true about their product(s).

or they will support HTTP3 coming soon.

Probably…however, until the Apache Software Foundation announces a roadmap, you can't be absolutely sure. The ASF rarely makes promises they can't keep. The schedule may be a bit fluid but the endpoint will be real (we're talking about volunteers here). In the meanwhile, they have a product called Apache Traffic Server (ATS) that may be useful to you. It's basically an HTTP3 caching proxy.

What is the real story about all of this posting.

Fear, Uncertainty and Doubt (FUD) by Litespeed…in order to gain some minuscule fraction of market share. Always distrust BS like this.

If you get the chance, ask Litespeed in earnest what evidence they have that HTTP3 is going to take over the world. You'll be surprised at the answer…if you even get one that makes any sense.

I don't see apache going to the Celestial Lab just because Litespeed says it is… Litespeed is in business to make money. They provide "open source" for street cred. They claim their open source software gets the same support and development as their pay-for products. Uh-huh…and pigs fly.

-- sw

Here's some information from RedHat regarding http 3. Note that even sites like LinkedIn and Twitter have not YET adapted over to http 3.

https://www.redhat.com/architect/http3

Only QUIC (which is a protocol that sits between UDP and HTTP3) has an RFC. HTTP3 is not standardized yet. No matter how close you may think it is, until it has an RFC number, it can't be considered "a standard".

I got burned by this once before… I put in a ton of work one of these "RFC draft" promises -- only to have the draft withdrawn later…rendering all my work worthless…and sending the product it was supposed to be part of back to the drawing board. You can imagine the powers that be were not amused…

This is probably what ASF is waiting for…and why Litespeed and the browser vendors that have announced "HTTP3 support" may get burned.

-- sw

Will apache2 change…most likely. Will apache2 disappear…maybe -- replaced by apache3… apache2 has an installed base and ecosystem that Litespeed can only salivate over. apache2 works; it's stable; it's well-documented; and tons of people use it (incl yours truly). Litespeed probably only wishes half of that were true about their product(s).

Fear, Uncertainty and Doubt (FUD) by Litespeed…in order to gain some minuscule fraction of market share. Always distrust BS like this.

I don't see apache going to the Celestial Lab just because Litespeed says it is… Litespeed is in business to make money. They provide "open source" for street cred. They claim their open source software gets the same support and development as their pay-for products. Uh-huh…and pigs fly.

Only QUIC (which is a protocol that sits between UDP and HTTP3) has an RFC. HTTP3 is not standardized yet. No matter how close you may think it is, until it has an RFC number, it can't be considered "a standard".

wow… ok seems you understand this very detailed..

Actually this is kind of what I suspected. Because Apache is free and popular for many years already and I thought probably Litespeed is just scaring people to think Apache is too old-fashioned and "slow" but it's not true

HTTP3 is not even the standard yet so just fake stuff from Litespeed. Kind of lame they tried to hurt Apache community and confusing people for $$$

Also found this one

https://wordpress.org/support/topic/litespeed-or-apache-for-wordpress/

"Your webhost is trying to bully you into paying for Litespeed because they keep up to 1/3 of your monthly Litespeed payment as commission. (This is why hosting companies so heavily promote Litespeed and CloudLinux, another product where a percentage of your monthly payment is “kicked back” as commission.) I suggest that you find a more honest/reputable hosting company."

"Your webhost is trying to bully you into paying for Litespeed because they keep up to 1/3 of your monthly Litespeed payment as commission…"

If someone I did business with did this, I'd drop them like a hot rock. There's an old fashioned name for this…bribery. See:

https://performingsongwriter.com/alan-freed-payola-scandal/

-- sw

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct