R: [SQU] Restricting IP's to specific WEB sites it works now.

Hi sqid users
Hi Henrik

This kind of restriction works fine now, i made this in squid.conf after a
suggest of Henrik:
(the site to restrict is www.trappex.com and this web is connected trough
links to: ns.trappex-xx.com and 194.xxx.xx.xx)

acl all src 0.0.0.0/0.0.0.0
acl one src 192.168.1.30 192.168.1.31 ...and so on
acl two src 192.168.1.100
acl two-sites dstdomain www.trappex.com ns.trappex-xx.com
acl two-ip dst 194.xxx.xx.xx

http_access allow one
http_access allow two two-sites
http_access allow two two-ip
http_access deny all

Thanx again Henrik

> -----Messaggio originale-----
> Da: hno@hem.passagen.se [mailto:hno@hem.passagen.se]
> Inviato: lunedi 18 dicembre 2000 7.58
> A: Robert Collins
> Cc: Squid Users Mailing List
> Oggetto: Re: [SQU] Squid & FTP
>
>
> Robert Collins wrote:
>
> > True. And I can see how mapping PUT onto FTP should work for
> the gateway.
> > But I don't see any requirements placed on the user interface
> wrt to the use
> > of PUT in combination with a HTTP proxy.
>
> True, but on the other hand there is no requirements to use GET either
> in order to retreive FTP objects from a HTTP proxy... The use of GET is
> simply from the fact that the protocol used is HTTP, and in HTTP the
> method for retreiving content is GET, just as PUT is the method for
> storing content.
>
> What a user interface supports and looks like is up to the implementator
> and is entirely outside RFC specifications. The specifications only tell
> the meaning of what goes over the wire or otherwise is exchanged between
> users (for example the meaning of URL's, and how they can be encoded to
> be transferred safely across different medias like email, news, html or
> whatever).
>
> --
> Henrik Nordstrom
> Squid Hacker
>
> --
> To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
>

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html