Re: [EMAIL PROTECTED] limit max number of simultaneous connections from same ip
Hello, Anton Krall wrote: Is there a way to limit the max number of httpd connections from a single ip? There is : just use iptables. Other than that, looking at your log, your situation is very normal : usually web browsers open about 4 concurrent connections when it has to fetch pictures related to a webpage... So it might be a bad idea to try to limit concurrent connections to only 1 serverside. For example: tcp0 30492 207.36.86.205:80162.84.172.175:50784 ESTABLISHED 31208/httpd tcp0 33396 207.36.86.205:80162.84.172.175:50785 ESTABLISHED 14245/httpd tcp0 0 207.36.86.205:80162.84.172.175:50782 ESTABLISHED 19402/httpd Limit 162.84.172.175 to only make one connection? - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jean-Christophe Montigny Responsable Commission Web, Association Planètes Responsable serveurs assoces.com, Association Planètes Etudiant de deuxième année à Grenoble Ecole de Management Majeure Conseil en Organisation des Systèmes d'Information begin:vcard fn:Jean-Christophe Montigny n:Montigny;Jean-Christophe org;quoted-printable:Association [EMAIL PROTECTED] adr;quoted-printable:;;12, rue Pierre S=C3=A9mard;Grenoble;FR;38000;France email;internet:[EMAIL PROTECTED] title:Responsable Com Web x-mozilla-html:FALSE url:http://planetes.assoces.com/ version:2.1 end:vcard - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [EMAIL PROTECTED] make URL's case insensitive - (opinion - OT)
-Original Message- From: Nick Kew [mailto:[EMAIL PROTECTED] It is HTTP, the protocol of the Web, that is case-sensitive. Anything that tries to pretend it's not is broken. Exactly. The whole concept of case-sensitivity is wrong-headed to begin with. The case of a letter is an essential part of its semantics and cannot be dispensed with without losing information. To give an example, the other night, I was in a restaurant and one of the items on the menu was Filets de perche d'Orange. In a case-insensitive world, you might expect your fish to come with orange sauce. But there was important information in the capital O in Orange... As it turns out the restaurant was called the Hotel D'Orange and so the menu was telling us that the dish was done in the special style of that hotel (garlic butter, actually). So the case of a single letter changed completely the semantics of the phrase and the taste of the fish. Filenames and URLs are meant for human consumption and so reflect the underlying semantics of human language (otherwise we'd just use inodes and IP addresses). So if case is important in our written language it must be important on a computer too. Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. -- Nick Kew - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Diese E-mail ist eine private und persönliche Kommunikation. Sie hat keinen Bezug zur Börsen- bzw. Geschäftstätigkeit der SWX Gruppe. This e-mail is of a private and personal nature. It is not related to the exchange or business activities of the SWX Group. Le présent e-mail est un message privé et personnel, sans rapport avec l'activité boursière du Groupe SWX. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company. - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] Apache2 + Apache-Tomact
Hello Leonardo, did you read the documentation? http://tomcat.apache.org/connectors-doc/index.html You will find all infos you need. Regards, Nicola Leonardo Hernandez wrote: Hello Somebody know how to configure Apache2 and Tomcat5 using jakarta-tomcat-connectors Regards -- Leonardo Hernández COMISION NACIONAL PARA EL CONOCIMIENTO Y USO DE LA BIODIVERSIDAD http://www.conabio.gob.mx/ Av. Liga Periférico-Insurgentes Sur # 4903 Parques del Pedregal, Tlalpan 14010, México D.F. México Teléfono: 5528-9140 Fax: 5528-9131 - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] Apache2 + Apache-Tomact
http://galatea.com/flashguides/home regards Dietmar Nicola Flucke [EMAIL PROTECTED] am 24.10.2005 08:42:03 Bitte antworten an users@httpd.apache.org An:users@httpd.apache.org Kopie: Thema: Re: [EMAIL PROTECTED] Apache2 + Apache-Tomact Hello Leonardo, did you read the documentation? http://tomcat.apache.org/connectors-doc/index.html You will find all infos you need. Regards, Nicola Leonardo Hernandez wrote: Hello Somebody know how to configure Apache2 and Tomcat5 using jakarta-tomcat-connectors Regards -- Leonardo Hernández COMISION NACIONAL PARA EL CONOCIMIENTO Y USO DE LA BIODIVERSIDAD http://www.conabio.gob.mx/ Av. Liga Periférico-Insurgentes Sur # 4903 Parques del Pedregal, Tlalpan 14010, México D.F. México Teléfono: 5528-9140 Fax: 5528-9131 - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] Apache IPv6 config help please
Now, I could be very wrong here.. I just did a bit of my own research on IPv6 (because I didn't know much about it) and apparantly the equivelant of 128.0.0.1 is ::1/128.. Don't you need to add the /128 at the end?On 10/24/05, Haifa Murad Hasan Abdulla Al Balooshi [EMAIL PROTECTED] wrote: I downloaded and installed the binary for apache_2.0.54-win32-x86-no_sslon windows XP service pack 2 (it works fine with IPv4)I want to enable IPv6In the config/httpd file, I addedlisten [::1] I also triedlisten [fe80::1]I got this error when I started apache:[Fri Oct 14 19:13:13 2005] [crit] (OS 11001)No such host is known.: alloc_listener: failed to set up sockaddr for [::1]Syntax error on line 121 of C:/Program Files/Apache Group/Apache2/conf/httpd.con f:Listen setup failedNote the errors or messages above, and press the ESC key to exit.18...Can anyone help me, please? - I want to know how to enable apache for IPv6- 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]-- Chris BabstockCell: 506-549-9623email: [EMAIL PROTECTED]
[EMAIL PROTECTED] Pass client certificate thorough apache to tomcat
Hi All, I have set up apache and tomcat where ssl requests are forwarded from apache to tomcat behind. Apache is handling the ssl issues and also requesting a client certificate. No problem so far, server and client certificates are exchanged during ssl session setup. What I need to do is to forward some of the information in the client certificate from apache to tomcat since application running on Tomcat needs this information. Can you guide me where to start? Thanks, Alpay
[EMAIL PROTECTED] Mass VHost, Access Rights (Apache 2.0)
Hi,
we are thinking about using mass virtual hosting to reduce the
configuration effort. Simplified we want each virtual host like
(${customer} is a variable for the host-name)
VirtualHost *:80
ServerName www.${customer}.com
ServerAlias customer.myhost.com
DocumentRoot /data/htdocs/customer
Location /awstats
AuthType Basic
AuthName Restricted Files
AuthUserFile /usr/local/apache/passwd/${customer}
Require valid-user
/Location
/VirtualHost
As I understand the documentation it is quite simple to set up a mass
VirtualHost-system. The only two things I could not find in the
documentation was this:
If I like to restrict access to a specific resource (here: /awstats) do
I have to specify the Location for each virtual host? Or is there a
possibility to specify the access restrictions in a more abstract way so
that we can specify the rule once? Ideally the solution would use
different password-files.
For any help, links to other documentation I'd be very happy
With regards
Tino
-
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: [EMAIL PROTECTED]
from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] Re: Apache2 + Apache-Tomact
Leonardo Hernandez said: Hello Somebody know how to configure Apache2 and Tomcat5 using jakarta-tomcat-connectors TFM on tomcat's website knows this. You should R it. Joost - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] Apache IPv6 config help please
On Mon, Oct 24, 2005 at 11:17:57AM +0400, Haifa Murad Hasan Abdulla Al Balooshi wrote: I want to enable IPv6 In the config/httpd file, I added listen [::1] This is close, but not quite there. You need to specify a port aswell; Listen [::1]:80 Will ask Apache to listen, on port 80, on the ::1 IPv6 loopback address. I also tried listen [fe80::1] This will not work, fe80::/16 is a link-local prefix, those addresses are not routed like ordinary unicast addresses, and you cannot listen on them without specifying an interface (which is not portable). Can anyone help me, please? - I want to know how to enable apache for IPv6 If you have IPv6 enabled on your host, and Apache has IPv6 built-in (an almost certainty if you are using 2.0.x), all you need do is; Listen 80 And Apache will listen in both IPv4 and IPv6. -- Colm MacCárthaighPublic Key: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] Re: Should be easy RewriteRule issue: mod_rewrite.
Hi Joshua (and all),
That worked great thanks, I had to take out the caret ^ you
had at the beginning of/servMainSite in the RewriteRule to make it work
but otherwise fine. Here's what I ended up with:
RewriteCond %{Request_URI}
!^/imgRewriteCond %{Request_URI}
!^/favicon.icoRewriteCond %{Request_URI}
!^/robots.txtRewriteCond %{Request_URI}
!^/cssRewriteCond %{Request_URI}
!^/menuRewriteCond %{Request_URI}
!^/servMainSiteRewriteRule ^/(.*)$ /servMainSite?inner=$1
[R,QSA,L]
I also added the R flag. Mainly because I always have done and
it has always worked for me! The documentation is so confusing though, can you
tell me if it is necessary? When I look at the RewriteLog I find that it has now
got a 302 is this what I want? Should I add a "permanent" flag?
Thanks,
Andoni
- Original Message -
From:
Joshua Slive
Newsgroups: gmane.comp.apache.user
Sent: Friday, October 21, 2005 7:25
PM
Subject: Re: Should be easy RewriteRule
issue: mod_rewrite.
On 10/21/05, Andoni [EMAIL PROTECTED]
wrote: Can you please help me with this RewriteRule. I am trying to
all users of my website to type in: www.mysite.com/area1
and have it re-written to: www.mysite.com/servMainSite?inner=area1
The slight complication is that /img, /css and /menu have to work as
of course does /servMainSite. At the moment I am getting an infinite
loop with the following: # RewriteRule
!^/(servMainSite.*|img.*|css.*|menu.*)/ /servMainSite?inner=$1
[R,L]There are several ways to do this. Here's
one:RewriteEngine OnRewriteCond %{Request_URI}
!^/imgRewriteCond %{Request_URI} !^/css...RewriteRule ^/(.*)
^/servMainSite?inner=$1
[QSA,L]Joshua.-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: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]For
additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] Re: Apache 2.0.55/win32 + OpenSSL 0.9.8a OWA Reverse Proxy Problems
Manuel Martin ([EMAIL PROTECTED]) wrote: since 2.0.55 a reverse SSL-proxy (on Windows 2000) which I setup for MS Exchange 2003 Outlook Web Access makes problems. The users stumbled over the problem that they cannot attach files to their emails. I tried it myself: the attachment seems to be uploaded to the server, but is not registered by Exchange. If I downgrade to 2.0.54 + OpenSSL 0.9.8 (I changed Apache while back to make that compilation possible) it works fine again. I really suspect this change to be the culprit: SECURITY: CAN-2005-2088 (cve.mitre.org) proxy: Correctly handle the Transfer-Encoding and Content-Length headers. Discard the request Content-Length whenever T-E: chunked is used, always passing one of either C-L or T-E: chunked whenever the request includes a request body. Resolves an entire class of proxy HTTP Request Splitting/Spoofing attacks. [William Rowe] Has anyone run or _not_ run into this problem with this configuration? Same problem here using apache 2.0.55 on FreeBSD 5.4. -- Please do not feed my mailbox, Swen still does his job well - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] Re: Re: Should be easy RewriteRule issue: mod_rewrite.
Hi, Removing the "R" broke it :-( Now when I go to www.mydomain.com/frontpage it does not re-write it at all, just giving me back a "page cannot be found" instead. Andoni. - Original Message - From: Joshua Slive Newsgroups: gmane.comp.apache.user Sent: Monday, October 24, 2005 3:23 PM Subject: Re: Re: Should be easy RewriteRule issue: mod_rewrite. On 10/24/05, Andoni [EMAIL PROTECTED] wrote: Now why could the documentation not have said that?The two types of redirect are discussed athttp://httpd.apache.org/docs/2.0/urlmapping.htmlIt is assumed that you wouldn't possibly dare trying to read themod_rewrite docs unless you are already a url-guru ;-)Seriously, there is a "rewrite" of the mod_rewrite docs underway athttp://httpd.apache.org/docs/2.0/rewrite/but it is kind of stalled.Joshua.-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: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
RE: [EMAIL PROTECTED] using cache in reverse proxy mode
The first response is not cacheable. It contains no cache validator (Etag, Last-Modified, Expires). The second is cacheable. You must disable cacheing of Set-Cookie using CacheIgnoreHeaders set-cookies With LogLevel debug you will get all the traces you need to understand why a response does not get cached. I would not use memory cache with Apache 2.0.54. I used it without problems with Apache 2.0.49, but I ran into core dumps in Apache 2.0.54. Probably does not do you much good anyway. -ascs -Original Message- From: Yavor Trapkov [mailto:[EMAIL PROTECTED] Sent: Saturday, October 22, 2005 9:54 PM To: users@httpd.apache.org Subject: Re: [EMAIL PROTECTED] using cache in reverse proxy mode Good point!, but it doesn't seems to be marked uncachable, here are two examples HTTP request sent, awaiting response... HTTP/1.1 200 OK Set-Cookie: JSESSIONID=8A211D396681857816C48E62C2E0D8A5; Path=/ Content-Type: text/html;charset=ISO-8859-1 Content-Length: 18 Date: Sat, 22 Oct 2005 19:47:57 GMT Server: Apache-Coyote/1.1 Connection: Keep-Alive Length: 18 [text/html] 21:47:49 (676.08 KB/s) - `index.jsp' saved [18/18] HTTP request sent, awaiting response... HTTP/1.1 200 OK ETag: W/18-113000941 Last-Modified: Sat, 22 Oct 2005 19:30:10 GMT Content-Type: text/html Content-Length: 18 Date: Sat, 22 Oct 2005 19:48:06 GMT Server: Apache-Coyote/1.1 Connection: Keep-Alive Length: 18 [text/html] 21:47:58 (258.50 KB/s) - `index.html' saved [18/18] - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] Re: Re: Should be easy RewriteRule issue: mod_rewrite.
On 10/24/05, Andoni [EMAIL PROTECTED] wrote: Hi, Removing the R broke it :-( Now when I go to www.mydomain.com/frontpage it does not re-write it at all, just giving me back a page cannot be found instead. Then you need to use the RewriteLog to figure out what is going on. One possibility is to add the PT flag to the RewriteRule, which is necessary if the URL will go through further aliasing. Joshua. - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] Flag to enable reading plain ASCII
Among the many flags in httpd.conf I cannot figure out what would enable the server to read both HTML and plain ASCII. This is pretty basic but I have not done it before -- somebody else did it, at a previous site, and is no longer available to tell me how. Can anyone tell me which flag to open and what to say or change? Ben -- From: Ben Gardiner Return address: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [EMAIL PROTECTED] make URL's case insensitive
Quoting Boyle Owen [EMAIL PROTECTED]:
-Original Message-
From: Nick Kew [mailto:[EMAIL PROTECTED]
It is HTTP, the protocol of the Web, that is case-sensitive.
Anything that tries to pretend it's not is broken.
Exactly.
The whole concept of case-sensitivity is wrong-headed to begin with. The
case of a letter is an essential part of its semantics and cannot be
dispensed with without losing information.
To give an example, the other night, I was in a restaurant and one of the
items on the menu was Filets de perche d'Orange. In a case-insensitive
world, you might expect your fish to come with orange sauce. But there was
important information in the capital O in Orange... As it turns out the
restaurant was called the Hotel D'Orange and so the menu was telling us
that the dish was done in the special style of that hotel (garlic butter,
actually). So the case of a single letter changed completely the semantics of
the phrase and the taste of the fish.
Filenames and URLs are meant for human consumption and so reflect the
underlying semantics of human language (otherwise we'd just use inodes and IP
addresses). So if case is important in our written language it must be
important on a computer too.
Hmmm, didn't consider this...(gah!)
On a different note, Joshua gave me the following use of mod_rewrite to make
URL's all lower case:
Well, you just changed your question. Mapping to all-lowercase is
actually possible, as opposed to general case-insensitivity which is
not possible (and, in addition, not advisable, since proxy caches,
search engines, etc are all case sensitive).
Something like:
RewriteEngine On
RewriteMap lc int:tolower
RewriteRule (.*) ${lc:$1} [R]
(The [R] on the end is not strictly necessary, but is highly
recommended unless you want many variants of your URLs to propogate to
search engines and caches.)
However, when I try this in apache (2.0.5x), I get the following message
returned to me in firefox 1.0.7:
redirection limit for this URL exceeded, unable to load requested page
It would appear that a infinite rewrite could be happening, but I'm not quite
sure as to how to solve the problem.
Bill
-
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: [EMAIL PROTECTED]
from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [EMAIL PROTECTED] make URL's case insensitive
At 10:44 -0700 10/24/05, [EMAIL PROTECTED] wrote, in part: . . . as opposed to general case-insensitivity which is not possible (and, in addition, not advisable, since proxy caches, search engines, etc are all case sensitive). Well, Google is case INsensitive and proud of it. I once complained explicitly because of things like the ON in ON Semiconductor or universal use of caps in part numbers for electronics. AD for Analog Devices zB. Their polite answer was, paraphrased a bit, get lost, we know what we're doing. Try searching for AND gates. Think Mac OX neXt. . . I have a local machine named Gallifrey running Linux. I place an entry for it into my /etc/hosts file pointing to 192.168.1.26. Asking Safari to access Apache at http://Gallifrey fails!. The Someone changes the URL to http://gallifrey. Placing a parallel entry in /etc/hosts named gallifrey fixes it up. The doctor deserves to have his home planet capitalized. It appears that OS neXt converts everything to lower case expecting a DNS server to be case insensitive, as per URL specifications, when its own nslookup fails when looking into a local hosts file. -- -- Halloween == Oct 31 == Dec 25 == Christmas -- - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] make URL's case insensitive
On 10/24/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
RewriteEngine On
RewriteMap lc int:tolower
RewriteRule (.*) ${lc:$1} [R]
However, when I try this in apache (2.0.5x), I get the following message
returned to me in firefox 1.0.7:
redirection limit for this URL exceeded, unable to load requested page
Try adding a
RewriteCond %{Request_URI} [A-Z]
before the RewriteRule to make sure it only triggers on URLs that have
some upper-case in them.
Joshua.
-
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: [EMAIL PROTECTED]
from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] make URL's case insensitive
Doug McNutt wrote: At 10:44 -0700 10/24/05, [EMAIL PROTECTED] wrote, in part: . . . as opposed to general case-insensitivity which is not possible (and, in addition, not advisable, since proxy caches, search engines, etc are all case sensitive). Well, Google is case INsensitive and proud of it. Try... http://www.google.com/preferences?hl=en http://www.google.com/Preferences?hl=en Query strings have nothing to do with resource paths. Think Mac OX neXt. . . I have a local machine named Gallifrey running Linux. I place an entry for it into my /etc/hosts file pointing to 192.168.1.26. Asking Safari to access Apache at http://Gallifrey fails!. The Someone changes the URL to http://gallifrey. Placing a parallel entry in /etc/hosts named gallifrey fixes it up. The doctor deserves to have his home planet capitalized. The HOSTNAME is case insensitive. The resource name is not. See the respective RFC's and STD documents. It appears that OS neXt converts everything to lower case expecting a DNS server to be case insensitive, as per URL specifications, when its own nslookup fails when looking into a local hosts file. That's a bug on OS neXt, but is inapplicable to this whole discussion. Scheme and hostname are case insensitive. User/Password is application-defined. Resource is case sensitive. Query string is application defined. None of this is germane to the discussion at hand :) Bill - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] make URL's case insensitive
Quoting Joshua Slive [EMAIL PROTECTED]:
On 10/24/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
RewriteEngine On
RewriteMap lc int:tolower
RewriteRule (.*) ${lc:$1} [R]
However, when I try this in apache (2.0.5x), I get the following message
returned to me in firefox 1.0.7:
redirection limit for this URL exceeded, unable to load requested page
Try adding a
RewriteCond %{Request_URI} [A-Z]
before the RewriteRule to make sure it only triggers on URLs that have
some upper-case in them.
That appears to have done the trick...I had MeMBeRs in the URL and it processed
it normally (I'll be testing this for a week to 10 days before placing it on
other web servers). How much CPU overhead would something like this add to the
web server itself (if you know offhand).
Thanks for the help, btw!
Bill
-
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: [EMAIL PROTECTED]
from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [EMAIL PROTECTED] using cache in reverse proxy mode
I put CacheIgnoreCacheControl on CacheIgnoreNoLastModon CacheIgnoreHeaders set-cookie and now debug LogLevel showes the content is cached, but some things doesn't make much sense: with disk cache: each time I send a request I get [Mon Oct 24 22:47:13 2005] [debug] mod_cache.c(114): incoming request is asking for a uncached version of /index.jsp, but we know better and are ignoring it [Mon Oct 24 22:47:13 2005] [debug] mod_disk_cache.c(371): disk_cache: Recalled cached URL info header server.domain.com/index.jsp? [Mon Oct 24 22:47:13 2005] [debug] mod_disk_cache.c(502): disk_cache: Recalled headers for URL server.domain.com/index.jsp? [Mon Oct 24 22:47:13 2005] [debug] proxy_http.c(67): proxy: HTTP: canonicalising URL //server.domain.com:8080/index.jsp [Mon Oct 24 22:47:13 2005] [debug] mod_proxy.c(418): Trying to run scheme_handler [Mon Oct 24 22:47:13 2005] [debug] proxy_http.c(1059): proxy: HTTP: serving URL http://server.domain.com:8080/index.jsp [Mon Oct 24 22:47:13 2005] [debug] proxy_http.c(186): proxy: HTTP connecting http://server.domain.com:8080/index.jsp to server.domain.com:8080 [Mon Oct 24 22:47:13 2005] [debug] proxy_util.c(1139): proxy: HTTP: fam 2 socket created to connect to server.domain.com [Mon Oct 24 22:47:13 2005] [debug] proxy_http.c(336): proxy: socket is connected [Mon Oct 24 22:47:13 2005] [debug] proxy_http.c(370): proxy: connection complete to x.x.x.x:8080 (server.domain.com) [Mon Oct 24 22:47:13 2005] [debug] proxy_http.c(893): proxy: start body send [Mon Oct 24 22:47:13 2005] [debug] mod_cache.c(556): cache: Caching url: /index.jsp [Mon Oct 24 22:47:13 2005] [debug] mod_disk_cache.c(645): disk_cache: Stored headers for URL server.domain.com/index.jsp? [Mon Oct 24 22:47:13 2005] [debug] mod_disk_cache.c(747): disk_cache: Body for URL server.domain.com/index.jsp? cached. [Mon Oct 24 22:47:13 2005] [debug] proxy_http.c(953): proxy: end body send i.e. each time I request the document it's requested from the application server, and then cached again, it seems it's never server from the cache ?!? If I use mem cache: it behaves in a similar way, the difference is that every 4-5 hits I get mod_cache.c(220): cache: running CACHE_OUT filter mod_cache.c(229): cache: serving /index.jsp but then again it targets the application server Shouldn't it server the already cached document from the disk/mem cache and not sending requests to the application server, at least that's what I'm trying to achieve - to reduse the load of the application servers. Another point, what will happen if the application server is not responding, then ideally the cached page should be shown. Regards Yavor Axel-Stéphane SMORGRAV [EMAIL PROTECTED] wrote: The first response is not cacheable. It contains no cache validator (Etag, Last-Modified, Expires). The second is cacheable. You must disable cacheing of Set-Cookie using CacheIgnoreHeaders set-cookies With LogLevel debug you will get all the traces you need to understand why a response does not get cached. I would not use memory cache with Apache 2.0.54. I used it without problems with Apache 2.0.49, but I ran into core dumps in Apache 2.0.54. Probably does not do you much good anyway. -ascs -Original Message- From: Yavor Trapkov [mailto:[EMAIL PROTECTED] Sent: Saturday, October 22, 2005 9:54 PM To: users@httpd.apache.org Subject: Re: [EMAIL PROTECTED] using cache in reverse proxy mode Good point!, but it doesn't seems to be marked uncachable, here are two examples HTTP request sent, awaiting response... HTTP/1.1 200 OK Set-Cookie: JSESSIONID=8A211D396681857816C48E62C2E0D8A5; Path=/ Content-Type: text/html;charset=ISO-8859-1 Content-Length: 18 Date: Sat, 22 Oct 2005 19:47:57 GMT Server: Apache-Coyote/1.1 Connection: Keep-Alive Length: 18 [text/html] 21:47:49 (676.08 KB/s) - `index.jsp' saved [18/18] HTTP request sent, awaiting response... HTTP/1.1 200 OK ETag: W/18-113000941 Last-Modified: Sat, 22 Oct 2005 19:30:10 GMT Content-Type: text/html Content-Length: 18 Date: Sat, 22 Oct 2005 19:48:06 GMT Server: Apache-Coyote/1.1 Connection: Keep-Alive Length: 18 [text/html] 21:47:58 (258.50 KB/s) - `index.html' saved [18/18] - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Yavor Trapkov visit me at http://trapkov.homelinux.org icq: 2030035 __ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those
Fwd: [EMAIL PROTECTED] Flag to enable reading plain ASCII
-- Forwarded message -- From: Joshua Slive [EMAIL PROTECTED] Date: Oct 24, 2005 12:41 PM Subject: Re: [EMAIL PROTECTED] Flag to enable reading plain ASCII To: [EMAIL PROTECTED] Please send your message to the list. Thanks. Joshua. On 10/24/05, Ben Gardiner [EMAIL PROTECTED] wrote: Thanks, Joshua, for responding. I haven't *done* anything yet. What I want is for callers to be able to read both .html files and plain ascii. I have about 16,000 plain ascii files (from ages ago when it was a BBS) which were readable at the previous site. I moved everything to godaddy, where I have a virtual dedicated server. And now the caller gets an error message You don't have the pemissions to read (name of file or directory/file) I have checked the permissions, they are all readable by outsiders. Next thing, I thought, is to re-configure the Apache server to clear up the problem. I have not done anything (yet) to the Apache configuration. My question is what do I need to do in order to enable callers to read the plain ascii files? Is this something that Apache can do, or is my problem in another area? It used to work, and work fine. What the caller saw was a page of directories, and clicking on any of them would produce a subpage of either files or directories. (I mean only the names. The caller had to click on a name to get the actual file.) I was assuming that the error message about permissions meant that httpd was unable to deliver the file or move the caller to the directory. The permissions are _rwxr_xr_x on the files, and drwxrwxrwx on the directories. Am I wrong about those permission settings? Any help would be much appreciated. The page was getting 5,000-10,000 hits a day in the past. Ben On 10/24/05, Joshua Slive [EMAIL PROTECTED] wrote: On 10/24/05, Ben Gardiner [EMAIL PROTECTED] wrote: Among the many flags in httpd.conf I cannot figure out what would enable the server to read both HTML and plain ASCII. This is pretty basic but I have not done it before -- somebody else did it, at a previous site, and is no longer available to tell me how. Can anyone tell me which flag to open and what to say or change? Nothing needs to be changed. Apache doesn't care about the contents of files. Perhaps if you explained exactly what you tried and exactly what the result was, we could better help. It always helps to include relevant log extracts. Joshua. -- From: Ben Gardiner Return address: [EMAIL PROTECTED] -- From: Ben Gardiner Return address: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] Flag to enable reading plain ASCII
On 10/24/05, Ben Gardiner [EMAIL PROTECTED] wrote: On 10/24/05, Ben Gardiner [EMAIL PROTECTED] wrote: Thanks, Joshua, for responding. I haven't *done* anything yet. What I want is for callers to be able to read both .html files and plain ascii. I have about 16,000 plain ascii files (from ages ago when it was a BBS) which were readable at the previous site. I moved everything to godaddy, where I have a virtual dedicated server. And now the caller gets an error message You don't have the pemissions to read (name of file or directory/file) I have checked the permissions, they are all readable by outsiders. First thing to do is check the apache error log. It will tell you what the problem is. As I mentioned earlier, apache does not inherently treat text files any different from html (other than sending a different Content-Type header). Joshua. - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] Multiple instances bound to separate IPs?
Is it possible to run two separate instances of Apache, both on port 80, but each bound to a different IP? So, for instance one, I'd have this in the httpd.conf: Listen 192.168.1.1:80 And in the other, I'd have have: Listen 192.168.1.2:80 If I started each with a specification of configuration file, would it work, or would I get an error about a service already bound to port 80? I'd start them like so /usr/local/apache2/bin/httpd -f /usr/local/apache2/conf/httpd.conf -k start /usr/local/apache2_php5/bin/httpd -f /usr/local/apache2_php5/conf/httpd.conf -k start Thanks in advance, Sean - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] Multiple instances bound to separate IPs?
Define your instance specific nonsense as pereach instance. I.e. Pid files It is how we did it in the old days prior to VHosts - Sent from my NYPL BlackBerry Handheld. - Original Message - From: Sean Brown [EMAIL PROTECTED] Sent: 10/24/2005 09:19 PM To: users@httpd.apache.org Subject: [EMAIL PROTECTED] Multiple instances bound to separate IPs? Is it possible to run two separate instances of Apache, both on port 80, but each bound to a different IP? So, for instance one, I'd have this in the httpd.conf: Listen 192.168.1.1:80 And in the other, I'd have have: Listen 192.168.1.2:80 If I started each with a specification of configuration file, would it work, or would I get an error about a service already bound to port 80? I'd start them like so /usr/local/apache2/bin/httpd -f /usr/local/apache2/conf/httpd.conf -k start /usr/local/apache2_php5/bin/httpd -f /usr/local/apache2_php5/conf/httpd.conf -k start Thanks in advance, Sean - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
