![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Apache 2.2 problem | mjdousti | UNIX for Dummies Questions & Answers | 6 | 12-21-2007 11:21 PM |
| Apache start problem | maheshsri | SUN Solaris | 1 | 03-13-2006 06:07 AM |
| Apache with SSL problem | b_manu78 | SUN Solaris | 2 | 03-23-2005 06:13 PM |
| HTTPS connection unix | rkumar28 | UNIX for Advanced & Expert Users | 2 | 06-24-2004 07:20 PM |
| out of inodes on https dev hd | josramon | Filesystems, Disks and Memory | 4 | 11-12-2002 01:08 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
hi folks.
i know that this is not a realī unix problem, itīs an apache-webserver problem, but maybe you can help me? i have installed apache & mod_ssl, done a certificate, and configured my server well, but apache only understands "http://servername", not "https://servername". any ideas? cheers, alex... |
|
|||||
|
Apache web-server is normally started as httpd and this runs on port 80. Apache web-server can also run on other ports on the same platform. When Apache web-server is started using SSL as https:// it is normally started as httpsd (or something like that) running on port 443.
If you don't have a web-service running on port 443 the https:// construct will not work (unless you specify a different port). For well-known SSL based web-services you will have the 443 listening socket. Most users of web-services run both httpd and httpsd so you should (may) have www-services running on both port 80 and port 443 with different listening (server) processes. I recommend you build a static version of httpd and a static version of httpsd first and not deal with the complexities of loadable apache modules. After you are comfortable with static version and version control, they you can decide is loadable modules makes sense for you. However, for new users, they add a layer of complexity that make life more difficult. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|