List of features that can't be used if you read from the httpd.conf

Discussion in 'General' started by closet geek, Mar 4, 2009.

  1. closet geek

    closet geek Well-Known Member


    We know, for example, that chroot of VirtualHosts can't be used when you use LiteSpeed's ability to read directly from the httpd.conf but we're struggling to find out what other features we would miss out on if we used LiteSpeed in this way.

    Does anyone else know of other features that aren't available when you read from the httpd.conf?

  2. closet geek

    closet geek Well-Known Member

    I'm not sure why this is being ignored. I think it's a perfectly valid question!

    Features are listed on this website which aren't available to users who use LiteSpeed in a very popular, recommended, configuration. I would simply like to be given a list of features that aren't available so I can make a proper decision before spending thousands of dollars on a product.

    I have also email sales twice and never received a response to this question. Others have been answered just not this one.
  3. anewday

    anewday Moderator

    I want to know too. I know connection and bandwidth throttling per vhost is one of them.
  4. gdtechindia

    gdtechindia Member

    i would also like to know, what we are missing in this case.
  5. closet geek

    closet geek Well-Known Member

    Another week goes by, still no answer. What are LiteSpeedTech trying to hide here? This might sounds silly to say but after 2 ignored Sales emails and now a forum posting ignored for 2 weeks it's hard to draw any other conclusion.

    Consider me a very disappointed potential customer.
  6. Tony

    Tony Well-Known Member

    The answer could be that they do not have a document outlining what features cannot be used via a httpd.conf.

    The easy answer is though what's unique to litespeed is probably not going to work via httpd.conf since there will be no configuration settings defined for it.
  7. closet geek

    closet geek Well-Known Member

    Not having a document is fine, but when multiple potential/actual customers ask for one isn't it good customer service to supply it or at least respond in some way? I'm not asking them to draw up an essay here just a quick list of features that wouldn't be available even the most obvious would be fine it doesn't have to be ridiculously fine-grained.

    This would seem to make sense. I don't see why, for example, LS can't create virtualhost XML files for virtualhosts it reads from the httpd.conf to enable there to be no need for this question at all (so all LS specific features can be placed there).

    I guess I'm just looking for transparency. If I'm attracted to LS due to feature X only to find it not available due to using LS in a commonly suggested and promoted way I'm not going to be happy.

  8. anewday

    anewday Moderator

    ^ I agree, shouldn't take long to just list some of the features. Also while we're at this, the zero downtime graceful restart is not true. Thirty seconds after the graceful restart, it will kill all existing connections (before the graceful restart was executed). This obviously won't affect normal websites without big downloads or streaming content.

Share This Page