You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by GMane <ro...@hotmail.com> on 2003/05/21 12:03:47 UTC
[users@httpd] Webalizer won't give country info
I have installed webalizer on my Mandrake 9.0 webserver. In the past
webalizer has been able to give me information about usage by country. Now,
however, all I get is "100.00% Country Unresolved/Unknown".
Is there any way to remedy this or is it not possible to get more
information?
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Re: Webalizer won't give country info
Posted by Sam <si...@adria-web.com>.
This is the tip I found online that helped me when I had those problems.
"If you really need built in DNS support, it's really quite simple, however
different distributions place the required headers and libraries in
different places, so the configure script fails to find them. In a nutshell,
you need the Berkeley DB libary, and it needs to be configured with V1.85
API support. Most Linux distributions already have this library present. If
you get errors about not finding the proper header file (db_185.h), locate
it on your system and create a symbolic link to it in the /usr/include
directory. You will also need to specify the correct library to use for the
header. This may mean that you need to first run the configure script, then
if the compile fails due to unresolved references, edit the Makefile and
change the -ldb (or -ldb1) reference to the correct library, such
as -ldb-3.2 for RedHat, or just -ldb for Slackware 8. Each distribution
either names the library something different, or puts it in a different
location, so you will have to play around with it on your distro to get it
to work. If the library is in some non-standard location, you may also need
to specify it's path using the --with-dblib=... switch when you run the
configure script. Bottom line is, if you don't really need it (and most
people don't), just compile without DNS support and let your web server do
the name lookups for you."
"To compile under RH 7.x or 8.x using DNS resolver, you must use this
command line:
./configure --enable-dns --with-db=/usr/include/db1
You must have the db1 and the db1-devel RPMs installed in order to do this."
Hope this helps
Sam
----- Original Message -----
From: "GMane" <ro...@hotmail.com>
To: <us...@httpd.apache.org>
Sent: Wednesday, May 21, 2003 3:05 PM
Subject: [users@httpd] Re: Webalizer won't give country info
>
> "Sam" <si...@adria-web.com> wrote in message
> news:004a01c31f82$ae1f4400$0d01a8c0@adriaweb...
> > > I have installed webalizer on my Mandrake 9.0 webserver. In the past
> > > webalizer has been able to give me information about usage by country.
> > Now,
> > > however, all I get is "100.00% Country Unresolved/Unknown".
> > >
> > > Is there any way to remedy this or is it not possible to get more
> > > information?
>
> > I am not sure, but I had a similar problem and I had to recompile
> webalizer
> > with --enable-dns option. Take a look at DNS.README.
> > Sam
> >
>
> Thanks. I think I'll try this option. When I try to run ./configure with
> the DNS option enabled I get:
>
> checking whether char is unsigned... (cached) no
> checking for dbopen... (cached) no
> checking for library containing dbopen... (cached) no
> configure: warning: You must have a V1.85 compatable DB library!
> configure: warning: DNS lookup code will be disabled...
>
> I have tried installing libdb but still get the same message. What am I
> missing? I'm using Mandrake 9.0
>
> Robert.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
[users@httpd] Re: Webalizer won't give country info
Posted by GMane <ro...@hotmail.com>.
"Sam" <si...@adria-web.com> wrote in message
news:004a01c31f82$ae1f4400$0d01a8c0@adriaweb...
> > I have installed webalizer on my Mandrake 9.0 webserver. In the past
> > webalizer has been able to give me information about usage by country.
> Now,
> > however, all I get is "100.00% Country Unresolved/Unknown".
> >
> > Is there any way to remedy this or is it not possible to get more
> > information?
> I am not sure, but I had a similar problem and I had to recompile
webalizer
> with --enable-dns option. Take a look at DNS.README.
> Sam
>
Thanks. I think I'll try this option. When I try to run ./configure with
the DNS option enabled I get:
checking whether char is unsigned... (cached) no
checking for dbopen... (cached) no
checking for library containing dbopen... (cached) no
configure: warning: You must have a V1.85 compatable DB library!
configure: warning: DNS lookup code will be disabled...
I have tried installing libdb but still get the same message. What am I
missing? I'm using Mandrake 9.0
Robert.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: [users@httpd] mod_rewrite help
Posted by Beau Hebert <bh...@c-quential.com>.
Thanks, but it appears that I may just have to sweep this one under the
rug. It doesn't seem that there is a way to rewrite the request (as I
have tried all suggestions) prior to the SSL Handshake. I think I am
stuck with dreaded Security Alert. My only solace is that the alert is
brought on by non-conventional use. It's not a huge deal. Alas, I often
fantasize of living in a perfect world.
I appreciate all of your responses.
Beau
-----Original Message-----
From: Beau Hebert [mailto:bhebert@c-quential.com]
Sent: Wednesday, May 21, 2003 4:28 PM
To: users@httpd.apache.org
Subject: RE: [users@httpd] mod_rewrite help
-----Original Message-----
From: Jurgen [mailto:apache@squarehosting.com]
Sent: Wednesday, May 21, 2003 4:28 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] mod_rewrite help
Hi,
Or this (it has to go into the VirtualHost configuration for the https
server):
RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ https://www.mydomain.com$1 [R]
it rewrites everything to www. if it doesn't start with www.
I am not sure if this will not help you, as the SSL connection is
established first and therefore I am afraid the browser will already
complain.
Jurgen
On Wed, 21 May 2003 10:28:20 -0700
Michael A Nachbaur <mi...@nachbaur.com> wrote:
> I think the following might work. You'll have to add it to your HTTPS
> VirtualHost.
>
> RewriteEngine On
> RewriteCond %{HTTP_HOST} ^mydomain.com$
> RewriteRule ^(.*)$ https://www.mydomain.com$1
[R]
>
> What this does (I think, I'm no mod_rewrite expert) is perform the
RewriteRule
> to redirect the browser to the full domain name only if the HTTP_HOST
request
> header is mydomain.com (minus the www.).
>
> On Wednesday 21 May 2003 08:08 am, Beau Hebert wrote:
> > First, a big thanks to all out in Apacheland for helping me rewrite
> > incoming http requests to https. It works like a charm. But, as
usual,
> > one success has led to another obstacle.
> >
> > As mentioned, all incoming HTTP requests are rewritten to HTTPS
using
> > mod_rewrite with the following code (thanks again Jurgen):
> >
> > RewriteEngine On
> > RewriteRule ^(.*)$ https://www.mydomain.com$1
> >
> > As a consequence to having all requests being HTTPS I also need to
have
> > all incoming requests contain www (i.e.
> > https://www.mydomain.com/login.php rather than simply
> > https://mydomain.com/login.php), otherwise the user receives an
alert
> > that the name on the Certificate doesn't match the website. This is
> > because the Secure Certificate is registered to the fully qualified
> > domain. So, my question: is there a way (either augmenting the code
> > above or including new code) so that if someone were to type
> > http://mydomnain.com/anypage.jsp, it would be rewritten to
> > https://www.mydomain.com/anypage.jsp.
> >
> > Thanks.
> > Beau
> >
> >
> >
> >
---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
>
> --
> Michael A Nachbaur <mi...@nachbaur.com>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server
Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: [users@httpd] mod_rewrite help
Posted by Beau Hebert <bh...@c-quential.com>.
-----Original Message-----
From: Jurgen [mailto:apache@squarehosting.com]
Sent: Wednesday, May 21, 2003 4:28 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] mod_rewrite help
Hi,
Or this (it has to go into the VirtualHost configuration for the https
server):
RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ https://www.mydomain.com$1 [R]
it rewrites everything to www. if it doesn't start with www.
I am not sure if this will not help you, as the SSL connection is
established first and therefore I am afraid the browser will already
complain.
Jurgen
On Wed, 21 May 2003 10:28:20 -0700
Michael A Nachbaur <mi...@nachbaur.com> wrote:
> I think the following might work. You'll have to add it to your HTTPS
> VirtualHost.
>
> RewriteEngine On
> RewriteCond %{HTTP_HOST} ^mydomain.com$
> RewriteRule ^(.*)$ https://www.mydomain.com$1
[R]
>
> What this does (I think, I'm no mod_rewrite expert) is perform the
RewriteRule
> to redirect the browser to the full domain name only if the HTTP_HOST
request
> header is mydomain.com (minus the www.).
>
> On Wednesday 21 May 2003 08:08 am, Beau Hebert wrote:
> > First, a big thanks to all out in Apacheland for helping me rewrite
> > incoming http requests to https. It works like a charm. But, as
usual,
> > one success has led to another obstacle.
> >
> > As mentioned, all incoming HTTP requests are rewritten to HTTPS
using
> > mod_rewrite with the following code (thanks again Jurgen):
> >
> > RewriteEngine On
> > RewriteRule ^(.*)$ https://www.mydomain.com$1
> >
> > As a consequence to having all requests being HTTPS I also need to
have
> > all incoming requests contain www (i.e.
> > https://www.mydomain.com/login.php rather than simply
> > https://mydomain.com/login.php), otherwise the user receives an
alert
> > that the name on the Certificate doesn't match the website. This is
> > because the Secure Certificate is registered to the fully qualified
> > domain. So, my question: is there a way (either augmenting the code
> > above or including new code) so that if someone were to type
> > http://mydomnain.com/anypage.jsp, it would be rewritten to
> > https://www.mydomain.com/anypage.jsp.
> >
> > Thanks.
> > Beau
> >
> >
> >
> >
---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
>
> --
> Michael A Nachbaur <mi...@nachbaur.com>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server
Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] mod_rewrite help
Posted by Jurgen <ap...@squarehosting.com>.
Hi,
Or this (it has to go into the VirtualHost configuration for the https server):
RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ https://www.mydomain.com$1 [R]
it rewrites everything to www. if it doesn't start with www.
I am not sure if this will not help you, as the SSL connection is established first and therefore I am afraid the browser will already complain.
Jurgen
On Wed, 21 May 2003 10:28:20 -0700
Michael A Nachbaur <mi...@nachbaur.com> wrote:
> I think the following might work. You'll have to add it to your HTTPS
> VirtualHost.
>
> RewriteEngine On
> RewriteCond %{HTTP_HOST} ^mydomain.com$
> RewriteRule ^(.*)$ https://www.mydomain.com$1 [R]
>
> What this does (I think, I'm no mod_rewrite expert) is perform the RewriteRule
> to redirect the browser to the full domain name only if the HTTP_HOST request
> header is mydomain.com (minus the www.).
>
> On Wednesday 21 May 2003 08:08 am, Beau Hebert wrote:
> > First, a big thanks to all out in Apacheland for helping me rewrite
> > incoming http requests to https. It works like a charm. But, as usual,
> > one success has led to another obstacle.
> >
> > As mentioned, all incoming HTTP requests are rewritten to HTTPS using
> > mod_rewrite with the following code (thanks again Jurgen):
> >
> > RewriteEngine On
> > RewriteRule ^(.*)$ https://www.mydomain.com$1
> >
> > As a consequence to having all requests being HTTPS I also need to have
> > all incoming requests contain www (i.e.
> > https://www.mydomain.com/login.php rather than simply
> > https://mydomain.com/login.php), otherwise the user receives an alert
> > that the name on the Certificate doesn't match the website. This is
> > because the Secure Certificate is registered to the fully qualified
> > domain. So, my question: is there a way (either augmenting the code
> > above or including new code) so that if someone were to type
> > http://mydomnain.com/anypage.jsp, it would be rewritten to
> > https://www.mydomain.com/anypage.jsp.
> >
> > Thanks.
> > Beau
> >
> >
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
>
> --
> Michael A Nachbaur <mi...@nachbaur.com>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] mod_rewrite help
Posted by Michael A Nachbaur <mi...@nachbaur.com>.
I think the following might work. You'll have to add it to your HTTPS
VirtualHost.
RewriteEngine On
RewriteCond %{HTTP_HOST} ^mydomain.com$
RewriteRule ^(.*)$ https://www.mydomain.com$1 [R]
What this does (I think, I'm no mod_rewrite expert) is perform the RewriteRule
to redirect the browser to the full domain name only if the HTTP_HOST request
header is mydomain.com (minus the www.).
On Wednesday 21 May 2003 08:08 am, Beau Hebert wrote:
> First, a big thanks to all out in Apacheland for helping me rewrite
> incoming http requests to https. It works like a charm. But, as usual,
> one success has led to another obstacle.
>
> As mentioned, all incoming HTTP requests are rewritten to HTTPS using
> mod_rewrite with the following code (thanks again Jurgen):
>
> RewriteEngine On
> RewriteRule ^(.*)$ https://www.mydomain.com$1
>
> As a consequence to having all requests being HTTPS I also need to have
> all incoming requests contain www (i.e.
> https://www.mydomain.com/login.php rather than simply
> https://mydomain.com/login.php), otherwise the user receives an alert
> that the name on the Certificate doesn't match the website. This is
> because the Secure Certificate is registered to the fully qualified
> domain. So, my question: is there a way (either augmenting the code
> above or including new code) so that if someone were to type
> http://mydomnain.com/anypage.jsp, it would be rewritten to
> https://www.mydomain.com/anypage.jsp.
>
> Thanks.
> Beau
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
--
Michael A Nachbaur <mi...@nachbaur.com>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: [users@httpd] mod_rewrite help
Posted by Beau Hebert <bh...@c-quential.com>.
No, the Rewrite rule does not tack on www. to https:// after accepting
the certificate. It sounds like what you're saying is that regardless, I
would need another Certificate for https://mydomain.com for any of this
to work. I was just hoping that I could rewrite the URL from https:// to
http://www. prior to the handshake to a) avoid the security alert and b)
not have to buy another certificate (which I wouldn't have done anyway).
Thanks for your help
Beau
-----Original Message-----
From: na11@daimlerchrysler.com [mailto:na11@daimlerchrysler.com]
Sent: Wednesday, May 21, 2003 12:17 PM
To: users@httpd.apache.org
Subject: RE: [users@httpd] mod_rewrite help
|For example if you go to http://mydomain.com, it works beautifully
rewriting
|to https://www.mydomain.com. However, it you go to https://mydomain.com
|it doesn't tack on the www., and consequently, the security alert pops
|up.
Does it tack on the www. after the security alert? Your certificate is
going to be specific to the DNS name of the site, www.mydomain.com in
this
case, and the SSL handshake has to happen before mod_rewrite can
evaluate
and redirect so there is no avoiding the security alert. Unless you had
mydomain.com resolve to once Apache instance with a cert for
mydomain.com
that redirected to www.mydomain.com which would be another Apache
instance
with a different SSL cert. You might be able to accomplish this with IP
based Virtual Hosts as well but you'd still need another certificate.
-Norm
|-----------------------------+-----------------------------------------
--|
| "Beau Hebert" |
|
| <bh...@c-quential.com> |
|
| |
To|
| 05/21/2003 12:06 PM |
<users@htt|
| |
pd.apache.|
| Please respond to | org>
|
| users@httpd.apache.org |
cc|
| |
|
| |
Subject|
| | RE:
|
| |
[users@htt|
| | pd]
|
| |
mod_rewrit|
| | e help
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|-----------------------------+-----------------------------------------
--|
The rule does work in that it rewrites all HTTP requests to https://www.
The problem is that it won't tack on www. to a https:// request. For
example if you go to http://mydomain.com, it works beautifully rewriting
to https://www.mydomain.com. However, it you go to https://mydomain.com
it doesn't tack on the www., and consequently, the security alert pops
up. So, I guess what I need in addition to the rule that is written is
for all individual https://mydomain.com requests written to
https://wwwmydomain.com. The current rule doesn't seem to affect this.
RewriteEngine On
RewriteRule ^(.*)$ https://www.mydomain.com$1 [R]
All of this code is written in the Port 80 Virtual Host
Any other suggestions?
Thanks again
Beau
-----Original Message-----
From: Paul Simon [mailto:wreckmybike@yahoo.com]
Sent: Wednesday, May 21, 2003 11:40 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] mod_rewrite help
I think what you are doing already solves the problem,
redirect (internally) everything to https://www...
I'd imagine putting an [R] on the rewrite rule might
force an external redirect to the www address,
stopping the alert.
-Paul
--- Beau Hebert <bh...@c-quential.com> wrote:
> First, a big thanks to all out in Apacheland for
> helping me rewrite
> incoming http requests to https. It works like a
> charm. But, as usual,
> one success has led to another obstacle.
>
> As mentioned, all incoming HTTP requests are
> rewritten to HTTPS using
> mod_rewrite with the following code (thanks again
> Jurgen):
>
> RewriteEngine On
> RewriteRule ^(.*)$ https://www.mydomain.com$1
>
> As a consequence to having all requests being HTTPS
> I also need to have
> all incoming requests contain www (i.e.
> https://www.mydomain.com/login.php rather than
> simply
> https://mydomain.com/login.php), otherwise the user
> receives an alert
> that the name on the Certificate doesn't match the
> website. This is
> because the Secure Certificate is registered to the
> fully qualified
> domain. So, my question: is there a way (either
> augmenting the code
> above or including new code) so that if someone were
> to type
> http://mydomnain.com/anypage.jsp, it would be
> rewritten to
> https://www.mydomain.com/anypage.jsp.
>
> Thanks.
> Beau
>
>
>
>
---------------------------------------------------------------------
> The official User-To-User support forum of the
> Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail:
> users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
>
=====
=====
'Ideals are like stars. We may never reach them, but we use them to
chart our course.' -- Unknown
=====
"Do not go where the path may lead, go instead where there is no path
and leave a trail" -- Ralph Waldo Emerson.
=====
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: [users@httpd] mod_rewrite help
Posted by na...@daimlerchrysler.com.
|For example if you go to http://mydomain.com, it works beautifully
rewriting
|to https://www.mydomain.com. However, it you go to https://mydomain.com
|it doesn't tack on the www., and consequently, the security alert pops
|up.
Does it tack on the www. after the security alert? Your certificate is
going to be specific to the DNS name of the site, www.mydomain.com in this
case, and the SSL handshake has to happen before mod_rewrite can evaluate
and redirect so there is no avoiding the security alert. Unless you had
mydomain.com resolve to once Apache instance with a cert for mydomain.com
that redirected to www.mydomain.com which would be another Apache instance
with a different SSL cert. You might be able to accomplish this with IP
based Virtual Hosts as well but you'd still need another certificate.
-Norm
|-----------------------------+-------------------------------------------|
| "Beau Hebert" | |
| <bh...@c-quential.com> | |
| | To|
| 05/21/2003 12:06 PM | <users@htt|
| | pd.apache.|
| Please respond to | org> |
| users@httpd.apache.org | cc|
| | |
| | Subject|
| | RE: |
| | [users@htt|
| | pd] |
| | mod_rewrit|
| | e help |
| | |
| | |
| | |
| | |
| | |
| | |
|-----------------------------+-------------------------------------------|
The rule does work in that it rewrites all HTTP requests to https://www.
The problem is that it won't tack on www. to a https:// request. For
example if you go to http://mydomain.com, it works beautifully rewriting
to https://www.mydomain.com. However, it you go to https://mydomain.com
it doesn't tack on the www., and consequently, the security alert pops
up. So, I guess what I need in addition to the rule that is written is
for all individual https://mydomain.com requests written to
https://wwwmydomain.com. The current rule doesn't seem to affect this.
RewriteEngine On
RewriteRule ^(.*)$ https://www.mydomain.com$1 [R]
All of this code is written in the Port 80 Virtual Host
Any other suggestions?
Thanks again
Beau
-----Original Message-----
From: Paul Simon [mailto:wreckmybike@yahoo.com]
Sent: Wednesday, May 21, 2003 11:40 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] mod_rewrite help
I think what you are doing already solves the problem,
redirect (internally) everything to https://www...
I'd imagine putting an [R] on the rewrite rule might
force an external redirect to the www address,
stopping the alert.
-Paul
--- Beau Hebert <bh...@c-quential.com> wrote:
> First, a big thanks to all out in Apacheland for
> helping me rewrite
> incoming http requests to https. It works like a
> charm. But, as usual,
> one success has led to another obstacle.
>
> As mentioned, all incoming HTTP requests are
> rewritten to HTTPS using
> mod_rewrite with the following code (thanks again
> Jurgen):
>
> RewriteEngine On
> RewriteRule ^(.*)$ https://www.mydomain.com$1
>
> As a consequence to having all requests being HTTPS
> I also need to have
> all incoming requests contain www (i.e.
> https://www.mydomain.com/login.php rather than
> simply
> https://mydomain.com/login.php), otherwise the user
> receives an alert
> that the name on the Certificate doesn't match the
> website. This is
> because the Secure Certificate is registered to the
> fully qualified
> domain. So, my question: is there a way (either
> augmenting the code
> above or including new code) so that if someone were
> to type
> http://mydomnain.com/anypage.jsp, it would be
> rewritten to
> https://www.mydomain.com/anypage.jsp.
>
> Thanks.
> Beau
>
>
>
>
---------------------------------------------------------------------
> The official User-To-User support forum of the
> Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail:
> users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
>
=====
=====
'Ideals are like stars. We may never reach them, but we use them to
chart our course.' -- Unknown
=====
"Do not go where the path may lead, go instead where there is no path
and leave a trail" -- Ralph Waldo Emerson.
=====
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: [users@httpd] mod_rewrite help
Posted by Beau Hebert <bh...@c-quential.com>.
The rule does work in that it rewrites all HTTP requests to https://www.
The problem is that it won't tack on www. to a https:// request. For
example if you go to http://mydomain.com, it works beautifully rewriting
to https://www.mydomain.com. However, it you go to https://mydomain.com
it doesn't tack on the www., and consequently, the security alert pops
up. So, I guess what I need in addition to the rule that is written is
for all individual https://mydomain.com requests written to
https://wwwmydomain.com. The current rule doesn't seem to affect this.
RewriteEngine On
RewriteRule ^(.*)$ https://www.mydomain.com$1 [R]
All of this code is written in the Port 80 Virtual Host
Any other suggestions?
Thanks again
Beau
-----Original Message-----
From: Paul Simon [mailto:wreckmybike@yahoo.com]
Sent: Wednesday, May 21, 2003 11:40 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] mod_rewrite help
I think what you are doing already solves the problem,
redirect (internally) everything to https://www...
I'd imagine putting an [R] on the rewrite rule might
force an external redirect to the www address,
stopping the alert.
-Paul
--- Beau Hebert <bh...@c-quential.com> wrote:
> First, a big thanks to all out in Apacheland for
> helping me rewrite
> incoming http requests to https. It works like a
> charm. But, as usual,
> one success has led to another obstacle.
>
> As mentioned, all incoming HTTP requests are
> rewritten to HTTPS using
> mod_rewrite with the following code (thanks again
> Jurgen):
>
> RewriteEngine On
> RewriteRule ^(.*)$ https://www.mydomain.com$1
>
> As a consequence to having all requests being HTTPS
> I also need to have
> all incoming requests contain www (i.e.
> https://www.mydomain.com/login.php rather than
> simply
> https://mydomain.com/login.php), otherwise the user
> receives an alert
> that the name on the Certificate doesn't match the
> website. This is
> because the Secure Certificate is registered to the
> fully qualified
> domain. So, my question: is there a way (either
> augmenting the code
> above or including new code) so that if someone were
> to type
> http://mydomnain.com/anypage.jsp, it would be
> rewritten to
> https://www.mydomain.com/anypage.jsp.
>
> Thanks.
> Beau
>
>
>
>
---------------------------------------------------------------------
> The official User-To-User support forum of the
> Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail:
> users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
>
=====
=====
'Ideals are like stars. We may never reach them, but we use them to
chart our course.' -- Unknown
=====
"Do not go where the path may lead, go instead where there is no path
and leave a trail" -- Ralph Waldo Emerson.
=====
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] mod_rewrite help
Posted by Paul Simon <wr...@yahoo.com>.
I think what you are doing already solves the problem,
redirect (internally) everything to https://www...
I'd imagine putting an [R] on the rewrite rule might
force an external redirect to the www address,
stopping the alert.
-Paul
--- Beau Hebert <bh...@c-quential.com> wrote:
> First, a big thanks to all out in Apacheland for
> helping me rewrite
> incoming http requests to https. It works like a
> charm. But, as usual,
> one success has led to another obstacle.
>
> As mentioned, all incoming HTTP requests are
> rewritten to HTTPS using
> mod_rewrite with the following code (thanks again
> Jurgen):
>
> RewriteEngine On
> RewriteRule ^(.*)$ https://www.mydomain.com$1
>
> As a consequence to having all requests being HTTPS
> I also need to have
> all incoming requests contain www (i.e.
> https://www.mydomain.com/login.php rather than
> simply
> https://mydomain.com/login.php), otherwise the user
> receives an alert
> that the name on the Certificate doesn't match the
> website. This is
> because the Secure Certificate is registered to the
> fully qualified
> domain. So, my question: is there a way (either
> augmenting the code
> above or including new code) so that if someone were
> to type
> http://mydomnain.com/anypage.jsp, it would be
> rewritten to
> https://www.mydomain.com/anypage.jsp.
>
> Thanks.
> Beau
>
>
>
>
---------------------------------------------------------------------
> The official User-To-User support forum of the
> Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for
> more info.
> To unsubscribe, e-mail:
> users-unsubscribe@httpd.apache.org
> " from the digest:
> users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail:
> users-help@httpd.apache.org
>
=====
=====
'Ideals are like stars. We may never reach them, but we use them to chart our course.' -- Unknown
=====
"Do not go where the path may lead, go instead where there is no path and leave a trail" -- Ralph Waldo Emerson.
=====
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
[users@httpd] mod_rewrite help
Posted by Beau Hebert <bh...@c-quential.com>.
First, a big thanks to all out in Apacheland for helping me rewrite
incoming http requests to https. It works like a charm. But, as usual,
one success has led to another obstacle.
As mentioned, all incoming HTTP requests are rewritten to HTTPS using
mod_rewrite with the following code (thanks again Jurgen):
RewriteEngine On
RewriteRule ^(.*)$ https://www.mydomain.com$1
As a consequence to having all requests being HTTPS I also need to have
all incoming requests contain www (i.e.
https://www.mydomain.com/login.php rather than simply
https://mydomain.com/login.php), otherwise the user receives an alert
that the name on the Certificate doesn't match the website. This is
because the Secure Certificate is registered to the fully qualified
domain. So, my question: is there a way (either augmenting the code
above or including new code) so that if someone were to type
http://mydomnain.com/anypage.jsp, it would be rewritten to
https://www.mydomain.com/anypage.jsp.
Thanks.
Beau
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Webalizer won't give country info
Posted by Sam <si...@adria-web.com>.
I am not sure, but I had a similar problem and I had to recompile webalizer
with --enable-dns option. Take a look at DNS.README.
Sam
----- Original Message -----
From: "GMane" <ro...@hotmail.com>
To: <us...@httpd.apache.org>
Sent: Wednesday, May 21, 2003 12:03 PM
Subject: [users@httpd] Webalizer won't give country info
> I have installed webalizer on my Mandrake 9.0 webserver. In the past
> webalizer has been able to give me information about usage by country.
Now,
> however, all I get is "100.00% Country Unresolved/Unknown".
>
> Is there any way to remedy this or is it not possible to get more
> information?
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org