Let's say you have a site blocked in the SonicWall SOHO. Messages in the log indicate that the site is blocked. An http GET request to that site for a .gif results in a black box with a red bar through it. The site *is* being blocked as far as what the client *gets back*. The question is, what's really happening on the outbound side. SonicWall seems to disagree with SonicWall about this. On the one hand, the log file the firewall mails me seems to imply that the *outbound* http GET request is dropped -- the logfile entry shows a source on the LAN and a destination which is the blocked site. That's good. But syslog shows the GET request and indicates yay many bytes sent, implying that the GET request did in fact get sent to the web site in question. So I'm left wondering what *REALLY* happens. Does the http GET request *really* go out the door to the blocked site or not? Does anybody know? Since getting the SonicWall (for my site at home) and looking at syslog I've started to get the willies about information some web sites are sending as arguments to GET requests -- even when I've got these sites on my Never list for cookies. --- #include <disclaimer.h> Jim Rosenberg Ross Mould 259 S. College St. Washington, PA 15301 (724) 222-7006 x 189 E-mail: [EMAIL PROTECTED] - [To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe firewalls" in the body of the message.]
