|
Home > Archive > Apache Server configuration support > January 2004 > HTTP & HTTPS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Hi ,
I am new to apache and would like know this..
1.I want to run all except one file of my site in HTTP and the remaining
one- authentication- file in HTTPS.
2.This has two solutions as outlined in
http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html
Yes, HTTP and HTTPS use different server ports, so there is no direct
conflict between them. Either run two separate server instances (one binds
to port 80, the other to port 443) or even use Apache's elegant virtual
hosting facility where you can easily create two virtual servers which
Apache dispatches: one responding to port 80 and speaking HTTP and one
responding to port 443 speaking HTTPS.
My question is , is there any configuration possible other than the above
methods?
Regards,
Biji Prathap
| |
| Davide Bianchi 2004-01-24, 2:34 am |
| biji@bdumail.com wrote:quote:
> 1.I want to run all except one file of my site in HTTP and the remaining
> one- authentication- file in HTTPS.
-zap-quote:
> My question is, is there any configuration possible other than the above
> methods?
Hu... what do you mean?
Davide
--
| MS-DOS didn't get as bad as it is overnight -- it took over ten years
| of careful development
|
| |
|
| we want to run the entire site in HTTP.But the for the login we are going
to use APAche's www authentication over SSL.We also want to be able to give
users an opportunity to type urls on their browser and get the site.So we
have the application server redirecting all initial requests on http to the
secured page , which would pop-up the authentication over SSL and then
transperantly getting the person back to HTTP channels for further browsing
the site.
So we need to have http and https running on the site.But we want to avoid
running virtual hosts if possible and totally avoid running two server
instances.
So i was asking if anyone knows about a configuration to achieve this
without vhosts or two server instances...
TIA,
biji
<biji@bdumail.com> wrote in message
news:buu421$m5d39$1@ID-147677.news.uni-berlin.de...quote:
> Hi ,
> I am new to apache and would like know this..
>
> 1.I want to run all except one file of my site in HTTP and the remaining
> one- authentication- file in HTTPS.
> 2.This has two solutions as outlined in
> http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html
>
> Yes, HTTP and HTTPS use different server ports, so there is no direct
> conflict between them. Either run two separate server instances (one binds
> to port 80, the other to port 443) or even use Apache's elegant virtual
> hosting facility where you can easily create two virtual servers which
> Apache dispatches: one responding to port 80 and speaking HTTP and one
> responding to port 443 speaking HTTPS.
>
> My question is , is there any configuration possible other than the above
> methods?
>
>
>
> Regards,
>
> Biji Prathap
>
>
>
>
>
>
| |
| Davide Bianchi 2004-01-24, 7:33 pm |
| biji@bdumail.com wrote:quote:
> So we need to have http and https running on the site.But we want to avoid
> running virtual hosts if possible and totally avoid running two server
> instances.
Explained like this, no, you have to use VHosts.
Davide
--
| The difference between math and physics is the difference between
| masturbation and sex. They're both messy, but physics can get you in
| much more trouble. -- Paul Tomblin & Malcom Ray
|
|
|
| |
| Richard Antony Burton 2004-01-24, 9:33 pm |
|
<biji@bdumail.com> wrote in message
news:buvob0$l99qg$1@ID-147677.news.uni-berlin.de...
quote:
> So we need to have http and https running on the site.But we want to avoid
> running virtual hosts if possible and totally avoid running two server
> instances.
You are going to have to use virtual hosting, else you have no container in
your httpd.conf in which to enable SSL, as you can only apply this directive
at the Server or vhost level.
The easiest way would be to use a pretty minimal vhost for your HTTPS, as it
will inherit the majority of the config - as long as you put the common
stuff in the main server section, rather than in a vhost for the HTTP side
of the site.
This way will allow the entire site to be accessed over both HTTP and HTTPS.
Then you can use a ditecory or location section with the SSLRequireSSL
directive to make sure the secure page can only be accessed over HTTPS.
Richard.
| |
|
| Thanks for the clarification....
"Richard Antony Burton" <richardaburton-NOSPAM-@hotmail.com> wrote in
message news:kHMQb.6520512$Id.1059194@news.easynews.com...quote:
>
> <biji@bdumail.com> wrote in message
> news:buvob0$l99qg$1@ID-147677.news.uni-berlin.de...
>
avoid[QUOTE][color=darkred]
>
> You are going to have to use virtual hosting, else you have no container
inquote:
> your httpd.conf in which to enable SSL, as you can only apply this
directivequote:
> at the Server or vhost level.
>
> The easiest way would be to use a pretty minimal vhost for your HTTPS, as
itquote:
> will inherit the majority of the config - as long as you put the common
> stuff in the main server section, rather than in a vhost for the HTTP side
> of the site.
>
> This way will allow the entire site to be accessed over both HTTP and
HTTPS.quote:
> Then you can use a ditecory or location section with the SSLRequireSSL
> directive to make sure the secure page can only be accessed over HTTPS.
>
> Richard.
>
>
|
|
|
|
|