Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: setenvif question



At 5:41 AM -0500 2/22/05, Robert Dell wrote:
Dan Shoop wrote:

At 7:02 PM -0500 2/21/05, Robert Dell wrote:

Ok, I THINK I have this right on the httpd.conf apache 1.33 file.

if the user agent is AOL's proxy server then it sets aol
if the request type is HEAD then head is set
if head and aol is set then blockaolproxy is set

SetEnvIf User-Agent ".*AOL.*" aol
SetEnvIf Request-Type ".*HEAD.*" head
SetEnvIf env=head & env=aol blockaolproxy

I'm not sure if I need parentheses on number 3


Either way I doubt it's valid. SetEnvIf takes a perl style regex, not a conditional.

will the above do what i THINK it will do?


I'm sorry, I can't read minds. What are you expecting it to do? How do you expect this to be useful?

WHat you expect it to do and be useful for might be wildly different than what I understand it to do.

before you start in on your "http user agent is not required http field and also can be spoofed", I know and the machines I want to block identify themselves as AOL (User Agent --> "Mozilla/4.0 (compatible; MSIE 6.0; AOL 9.0; Windows NT 5.0)")

You're misinterpreting what I said.

I have no idea how you'd plan to use this later, so I can't tell what you're thinking to do.

so, I want to block access to those that identify themselves with AOL in the user agent field AND send a head request, that's all. AOL keeps sending 20-30 head requests per second every 2-3 hours from their proxy server (always different servers) for the same GIF image in my site that there's no link on my site to.

Checking to see if it's changed presumably and needs to be recached.

They don't even request robots.txt to see if they are allowed.

It's not a robot activity, it sounds like their cache.

You see what I want to do?

No. You haven't explained how setting an environment variable will help you.

I want only AOL to get 401 errors when they access my site and then only when they head my files.

Mmmm... A 401 would be an entirely wrong response to send in such a case. A 401 normally triggers yet another request. Perhaps your wild and woolly authorization scheme is the root cause in the first place. ;)


Sounds like you really want to mark the image as no-cache.

And I still don't see how creating an environment variable here helps...
--

-dhan

------------------------------------------------------------------------
Dan Shoop                                                   AIM: iWiring
Systems & Networks Architect                     http://www.iwiring.net/
email@hidden                                 http://www.ustsvs.com/

pgp key fingerprint: FAC0 9434 B5A5 24A8 D0AF  12B1 7840 3BE7 3736 DE0B

iWiring designs and supports Internet systems and networks based on
Mac OS X, unix, and Open Source application technologies and offers
24x7, guaranteed support to registered clients, at affordable rates.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden

This email sent to email@hidden
References: 
 >setenvif question (From: Robert Dell <email@hidden>)
 >Re: setenvif question (From: Dan Shoop <email@hidden>)
 >Re: setenvif question (From: Robert Dell <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.