Removal of references to LiteSpeed

Discussion in 'General' started by XN-Matt, Apr 6, 2011.

  1. XN-Matt

    XN-Matt Well-Known Member

    I've asked this before, have been assured it would be implemented in a later release, it never is.

    When changing "Server Signature" to hide everything, any references to LiteSpeed should be removed but they are not.

    We can remove the footer on index pages by a simple page edit, fair enough. However, error pages are a different story.

    A single server-wide setting should be applied but isn't. Why should we have to pay for software which then links to the software suppliers website. Why should paying customers, for paid software, advertise for free?

    Asking for this before gives the standard, non-helpful response of use an error page to which I have asked how to apply one globally when using cPanel which never gets any sort of helpful response.

    So, when are you actually going to make that configuration option removal all references to LiteSpeed?
  2. webizen

    webizen Well-Known Member

  3. XN-Matt

    XN-Matt Well-Known Member

    Well thanks for answering my post with something completely useless.

    How about you re-read my post and actually answer the queries.

    I cannot do what you have suggested as we use cPanel and we should NOT have to do stuff to remove your adverts for each individual site.

    We want it gone. We pay for the software and we shouldn't have to advertise for you.
  4. webizen

    webizen Well-Known Member

    You can customize these error pages by modify ErrorDocument directive in /usr/local/apache/conf/include/errordocument.conf which is why the reference thread is given.

    Take 403 error page, for example, you can use default 403 page as follows:

    ErrorDocument 403 /403.shtml
    Alias /403.shtml /usr/local/apache/htdocs/403.shtml
    Alias /cp_errordocument.shtml /usr/local/apache/htdocs/cp_errordocument.shtml
    Where cp_errordocument.shtml is referenced in 403.shtml.


    ErrorDocument 403 "You are NOT allowed to access"
    in case someone would like to use their own error page (override global error page), define ErrorDocument directive in local .htaccess with a different URL (local) such as:
    ErrorDocument 403 /local403.shtml
  5. DanEZPZ

    DanEZPZ Well-Known Member

    That still doesn't answer his question...
  6. webizen

    webizen Well-Known Member

    no eta on configuration option. for the time being, just use custom error page to hide server signature.
  7. XN-Matt

    XN-Matt Well-Known Member

    Last edited: Apr 10, 2011
  8. XN-Matt

    XN-Matt Well-Known Member

    So nearly three weeks for any kind of support response.

    No wonder you've removed that from your helpdesk so you can ignore issues like this!
  9. webizen

    webizen Well-Known Member

    since there is a work around (as described above), priority to make code change becomes low. that's the reason of no ETA.
  10. XN-Matt

    XN-Matt Well-Known Member

    The work arounds do not work as documented for server-wide implementations when using cPanel, so it should be higher but also to point out, this was assured years ago.

    Over 2 years we were assured it would be implemented in the next version, of which there have been several since.

    You're also still yet to answer why any paying customer should have to advertise your software that has been PAID for.
  11. webizen

    webizen Well-Known Member

    The work around also works for individual vhost as stated earlier.

  12. XN-Matt

    XN-Matt Well-Known Member

    And if you care to re-read, we should not have to do this for each and every site.

    It should not be enabled in the first instance but as it is, there needs to be a way to disable globally. As such, there is no work around and as such, when is it going to be fixed.

    Do you think 2 years is an acceptable wait?

    Also, I'll ask again as it keeps getting ignored:

    You're also still yet to answer why any paying customer should have to advertise your software that has been PAID for.
  13. webizen

    webizen Well-Known Member

    if you look for a global solution, use your default cpanel errordoc or customize the default errdoc.

    that said, the work around cover all you need (global or individual). iow, the way to not advertise the software is already provided.
  14. XN-Matt

    XN-Matt Well-Known Member

    Once again: Do you think 2 years is an acceptable wait?
  15. webizen

    webizen Well-Known Member

    if a solution/workaround already addressed the issue and is easy to implement, why not use it or even use it right away? that's why no eta for making configuration option (your desired change) available at this point as we have other higher priority items to address which is understandable. you could wait. but that's your choice.

    that said, the question "Do you think 2 years is an acceptable wait?" is really for you instead.
    Last edited: Apr 22, 2011
  16. XN-Matt

    XN-Matt Well-Known Member

    Not really..

    Lets go through this again. One of your staff 2 years ago said it would be in a next release.

    We're several releases on and nothing. So the question is not for me and you're response is completely stupid.

    So answer the query; do you think 2 years of waiting after one of your staff said it would be sorted is acceptable. No is the answer, if you're unsure of how to answer it.

    Why not answer it and all the the questions that you've ignored!
  17. webizen

    webizen Well-Known Member

    thought you asked about the wait time you spent for the last 2 years. but if you meant for waiting for another 2 years, i can not tell you for sure since we have no eta.

Share This Page