The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

secure and non-secure access to webmail through the same URL?

Discussion in 'E-mail Discussions' started by danimal, Aug 21, 2006.

  1. danimal

    danimal Well-Known Member

    Joined:
    Jul 14, 2003
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    I've done some digging but haven't found this exact question/scenario, so...

    I want to be able to have certain clients able to go to: https://clientdomain.com/webmail/ and have that redirect to the secure version (2096). I don't want to set this system-wide, though, because as near as I understand it, it just makes http://whatever.com/webmail/ redirect to https://whatever.com:2096/ (from the Tweak Settings)

    I want my clients to be able to either do:
    http://clientdomain.com/webmail/ -> use 2095 (insecure)
    https://clientdomain.com/webmail/ -> use 2096 (secure)

    I suspect that I can't just do this by hacking /usr/local/cpanel/cgi-sys/ scripts, nor with .htaccess rewrite magic. I suspect I need to set up an SSL cert for the client and then do some redirect.

    But I'm hoping I'm wrong. Is there an easy way someone can suggest to make this happen?

    What I don't want is to force system-wide the http -> https for webmail.

    Actually, I'd like this to be a general system setting, but not like the Tweak Settings option. That is to say, I'd like to have some general setting that says if "/webmail" is called, check the "http vs https" and redirect accordingly. It seems that /usr/local/cpanel/cgi-sys/wredirect.cgi should already do this, but it doesn't. I.e. going to "https://clientdomain.com/webmail/" just gives a browser failure ("connection terminated unexpectedly").

    I can do a php or htaccess redirect for something like:
    http://clientdomain.com/swebmail/ -> https://clientdomain.com:2096/

    But I really like the elegance of the same URL but with http for insecure (2095) and https for secure (2096). It seems nice and neat to me.

    Thoughts?

    Thanks!

    -Danimal :cool:
     
    #1 danimal, Aug 21, 2006
    Last edited: Aug 21, 2006
  2. danimal

    danimal Well-Known Member

    Joined:
    Jul 14, 2003
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
Loading...

Share This Page