Dan Kuykendall wrote:
> So at this point I have to choose between HTTP and HTTPS. The two just
> wont work together. Apache doesnt even log connection attempts, because
> it doesnt even seem to have the port open.
>
> Does anyone know why this is happening?
HTTP and HTTPS definitely do work on
Could you post your httpd.conf file so we can see more information? It's
probably because you don't have a virtual host section for http and the
server will default to https if ssl support is included.
John
At 12:36 PM 4/17/2000 -0700, you wrote:
>I did a fresh install of RedHat 6.2
>compiled an
Have your tried to add
listen ip-address:80
also to the configuration files
I think that if you do the SSL-stuff he only listen to port 443 for the
moment.
Mike King wrote:
>
> Don't give up, this should work, although what you can do if you have
> to is
> run two processes, use httpd for no
Full_Name: Piet Ruyssinck
Version: 2.6.3-1.3.12
OS: Solaris
Submission from: (NULL) (157.193.44.18)
I have an apache 1.3.12 webserver running over SSL (via mod_ssl). SSL,
of course, because I'm doing Basic Authentication and I dont want my
users' passwords to be eavesdropped upon.
Let the URL
I did install apache 1.3.12 + openssl 0.9.5a + mod_ssl
2.6.2-1.3.12
after the installation, I did test for https ...
I did ./apachectl startssl
everything goes normal .. I show it to my manager :)
Then, this morning, I rebooted the server ...
after that, it seems that the old httpd was running,
Don't know if I'm right with my question on this list...
I have a request from a customer to build a secure reverse proxy. The
proxy (placed in the DMZ) should accept SSL connections from the
outside (no problem, mod_ssl). It should then forward the HTTP request
on another secure connection to a
On Tue, 18 Apr 2000, Joe Ammann wrote:
> Now mod_proxy can obviously not forward https connections. It doesn't
> know anything about SSL. And I could not find any information that
> such a thing has already been done.
I assume you are talking about mod_proxy on apache? We use it this way quite
http://www.apache-ssl.org/#mod_ssl
cheers,
Adam
samuel C wrote:
>
> Hi there.. I (like most humans) have some problems in my life.. I'm not
> expecting you to help me solve all of them, but surely will do with this
> one:
>
> I'm using
> Linux RedHat6.1
> apache 1.3.12
>
Hi there.. I (like most humans) have some problems in my life.. I'm not
expecting you to help me solve all of them, but surely will do with this
one:
I'm using
Linux RedHat6.1
apache 1.3.12
open-SSL 0.9.5a
mod_ssl-2.6.2-1.3.12
all compiled, installed and apparen
Since SSL is invoked before the HTTP request can be decrypted, the 401
response should NOT be returned to the browser. Therefore it would appear
that your configuration is flawed, allowing HTTP access to the virtual host
or directory with authentication enabled.
> -Original Message-
> Fr
It is impossible for a non-SSL client to speak with Apache/mod_ssl over an
SSL-enabled port. This means that it's impossible, as well, for the
client to get the "401 Authorization Required" message, since SSL must be
established for the actual httpd to even -see- the request.
Here's the procedur
It is impossible for a non-SSL client to speak with Apache/mod_ssl over an
SSL-enabled port. This means that it's impossible, as well, for the
client to get the "401 Authorization Required" message, since SSL must be
established for the actual httpd to even -see- the request.
Here's the procedur
On Tue, Apr 18, 2000 at 03:52:45PM +0200, Joe Ammann wrote:
> I have a request from a customer to build a secure reverse proxy. The
> proxy (placed in the DMZ) should accept SSL connections from the
> outside (no problem, mod_ssl). It should then forward the HTTP request
> on another secure connec
Well, I gave up. The problem was something I could not figure out, so I
when to the modssl.org contrib page and downloaded an apache-mod_ssl src
rpm and did a compile of that. I also had to grab the php-mod_ssl and
build and install it as well.
Now everything works fine. I didnt have time to full
Greetings,
Hope this is the right place to ask this, but I am
running into brick walls else where.
I need to convert a Thawte cert that was created and
is being used on an IIS server to work with
Apache/mod_ssl.
The Apache server is using the following:
Apache 1.3.12
Mod_SSL 2.6.3-1.3.12
OpenSS
In the usual place: http://www.modssl.org/contrib/
--
Magnus Stenman mailto:[EMAIL PROTECTED] http://www.hkust.se
Get it up, keep it up. Linux -- Viagra for your PC
__
Apache Interface to OpenSSL (mod_ssl)
Firstly copy apachectl to /etc/init.d (or link it), remove apache in
/etc/init.d if
you have old apache installed, then update-rc.d apache remove
to remove link from /etc/rc?.d, then update-rc.d apachectl S91 K20 to all
apachectl
into startup code. in apachectl, change the script so that the code
Hello,
Why is better to use "RewriteRule" than traditionnal "ProxyPass"
directive ?
Do you have an example.
Sylvain
Michael J Schout wrote:
>
> On Tue, 18 Apr 2000, Joe Ammann wrote:
>
> > Now mod_proxy can obviously not forward https connections. It doesn't
> > know anything about SSL. And I
18 matches
Mail list logo
