• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: URL filtering / IP Filter NKE
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: URL filtering / IP Filter NKE


  • Subject: Re: URL filtering / IP Filter NKE
  • From: Deena Awate <email@hidden>
  • Date: Wed, 22 Jun 2011 03:46:11 -0700 (PDT)

Hello,

First thanks for your reply which is very informative. I had tried my hands on option B. Through socket filter I could get just the IP address and not the URL. So I switched over to IP filter. The error returned from socket filter was informative but I am unable to achieve the same through IP filter. 
I looked around for synthesising a connection reset, but could not find how to do it. Some info on this will be useful. On Windows we do a connection reset.
Point C is also a good option that I can look at. It will be very helpful if you give me some guidance on how to a reset a connection.

Thanks,
Deena


--- On Wed, 6/22/11, Quinn "The Eskimo!" <email@hidden> wrote:

From: Quinn "The Eskimo!" <email@hidden>
Subject: Re: URL filtering / IP Filter NKE
To: "Mac Network Programming" <email@hidden>
Date: Wednesday, June 22, 2011, 3:37 PM


On 22 Jun 2011, at 09:38, Deena Awate wrote:

> Does the message that is displayed in the browser not depend on the value that I return from the IP filter NKE.

No, it does not, because you're working at the IP layer.  At the IP layer you can only choose to either forward the packet or not.  If you forward the packet, the connection goes through, if it don't, the connection will eventually time out.

You have a number of choices here:

A. You can synthesise a connection reset.  The browser will then promptly display a "connection refused" message.  This is probably an improvement, but it's probably not the best UI.

B. You can move up to the socket layer, at which point the error returned by your socket filter will be seen by the browser.  It's still likely to display an unhelpful message though.

C. You can synthesise a redirect to a page that displays an explanation of what's going wrong.

Option C is probably your best choice UI-wise.

Note that combining these options may be your best choice.  For example, it would be easier to implement option C if you moved up to the socket layer (option B).

S+E
--
Quinn "The Eskimo!"                    <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: URL filtering / IP Filter NKE
      • From: "Quinn \"The Eskimo!\"" <email@hidden>
    • Re: URL filtering / IP Filter NKE
      • From: Jens Alfke <email@hidden>
References: 
 >Re: URL filtering / IP Filter NKE (From: "Quinn \"The Eskimo!\"" <email@hidden>)

  • Prev by Date: Re: URL filtering / IP Filter NKE
  • Next by Date: Re: URL filtering / IP Filter NKE
  • Previous by thread: Re: URL filtering / IP Filter NKE
  • Next by thread: Re: URL filtering / IP Filter NKE
  • Index(es):
    • Date
    • Thread