User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6a) Gecko/20031009 Camino/0.7+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6a) Gecko/20031009 Camino/0.7+ Before I just upgraded Camino from about a month ago nightly build, it was properly using the OSX lookupd to find hosts. Now, it seems it is using its own mechanism to find hosts. The way I know this is not working in Camino and my machine is working is that Safari works properly. There is bug #194476, but that is a different problem so don't close this as a duplicate of that one. Here is my lookupd hosts configuration: lookupd -configuration LookupOrder: CacheAgent FFAgent DNSAgent ValidateCache: NO _config_name: Host Configuration name: hosts Here is my /etc/hosts 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost 0.0.0.0 a.tribalfusion.com Now, when I go to friendster.com using this version of Camino, I see the ads which are served by a.tribalfusion.com. Prviously it didn't show any ads. If I use Safari, I don't see the ads. I also modified my lookupd configuration and removed DNSAgent to confirm that lookupd is properly reading its configuration and that is true. It is as if Camino isn't using lookupd at all! I also just upgraded to OSX 10.2.8 and thought it might be something with the new version of OSX, but the lookupd version is the same as what is on 10.2.6. The fact that Safari works also confirms that it isn't a difference in OSX versions that is causing the problems. I'm a bit surprised no one else has reported this issue. Reproducible: Always Steps to Reproduce: see above Actual Results: I saw the ads. Expected Results: Don't show me the ads. =)

darin? did anything change?

I would love it if someone would try to just duplicate the problem and see if they are having it as well. It is very easy to do: http://www.macfora.com/forums/index.php?showtopic=6539 http://www.google.com/search?q=niutil%20dnsagent thanks!

what versions of gecko are we comparing here? was the old version of camino using the 1.0 branch builds? i haven't been following camino, so i don't know what a one month old build means. also i have no access to a mac with which to test this. the patch for bug 205726 recently went into the tree. that should not have had too much affect on the OSX build, though possibly it means that we are now calling getaddrinfo instead of gethostbyname on OSX.

adding a line like this to /etc/hosts 0.0.0.0 a.tribalfusion.com works fine (i.e., blocks URLs from loading from that host) with yesterday's trunk build under linux (RH9). again, without access to a mac, there's not much i can do with this bug. it might be useful if someone provided a mozilla socket log. there are instructions on this site which explain how to capture this log: http://www.mozilla.org/projects/netlib/http/http-debugging.html all i need is to see NSPR_LOG_MODULES=nsSocketTransport:5 thx!

exerpts from the log file: -------------------------- 29141392[1c23b60]: trying address: 0.0.0.0 ... 29141392[1c23b60]: connection failed! [reason=804b000d] ... 29141392[1c23b60]: nsSocketTransport::RecoverFromError [this=2df1770 state=3 cond=804b000d] ... 29141392[1c23b60]: trying again with next ip address ... 29141392[1c23b60]: trying address: 208.185.101.168 -------------------------- mozilla-trunk> host a.tribalfusion.com a.tribalfusion.com has address 208.185.101.168 so, the conclusion i'd draw is that OSX is giving the application both 0.0.0.0 and 208.185.101.168 as possible choices for a.tribalfusion.com. since in reality servers can be multi-homed, there is nothing mozilla can or should do to work around this behavior. i'd suggest filing a bug against the Apples since this is clearly a system issue. most likely we are now calling getaddrinfo instead of gethostbyname on OSX, and that probably explains the difference in behavior. we are calling getaddrinfo in order to support IPv6, and moreover it is the preferred way to do host resolution. i think this bug report is INVALID.

heh.. "the Apples".. not sure where that came from. i meant, "Apple" of course ;)

I understand that none of you seem to be OSX users (bah! =)), but I think that you should switch back to using gethostbyname on OSX for three reasons: #1. the number of people using IPv6 at this point is minimal compared with the number still using IPv4. As with browser compatibility wars, sometimes it is best to compromise with what the end user sees and wants as part of the user experience. #2. This broke functionality of the browser that is extremely useful. I don't want to see ads and I really like this browser and don't want to have to switch back to using Safari. Put yourself in my seat. I also don't expect that this is going to be the last time we hear about this issue. As soon as all of the OSX users out there who use a hosts file for blocking ads get the new version of Mozilla, they are going to ask the same questions as I am. #3. According to the OSX man page for getaddrinfo on 10.2.8, the implementation is still experimental and non-standard and therefore can be taken as something to not rely on as the preferred way to do things: This implementation is still very experimental and non-standard. The current implementation assumes a one-to-one relationship between inter- faces and links, which is not necessarily true according to the specifi- cation. I will file a bug report with Apple about this issue, however, I think that until that bug is fixed (does anyone have a copy of Panther to try?), the previous 'working' behavior should be restored on OSX. Maybe even have Mozilla conditionally use getaddrinfo only on 10.3 and on 10.2 go back to using gethostbyname? Thank you for your consideration on this matter.

I filed this as problem ID 3454903 with Apple.

jon: ok, maybe there is something we can do... hmm.. i wonder if other BSDs behave similarly. wtc: do you have any thoughts on this bug? apparently it seems that getaddrinfo returns results from both /etc/hosts and DNS. this breaks the ad blocking technique of listing ad servers under 0.0.0.0 to bypass DNS lookup. i suspect OSX is broken in doing this, but maybe there is no promise that it will not query both /etc/hosts and DNS. apparently, if we switch to calling gethostbyname, this problem goes away. that makes me suspect that the behavior getaddrinfo is unintended. one solution is probably to define _PR_INET6_PROBE, so that we will only call getaddrinfo on IPv6 enabled clients.

I think this pretty much says it...so, can I get you guys to put it back the way it was on 10.2 now? thanks! ------ Forwarded Message From: Marc Majka <majka@apple.com> Date: Fri, 17 Oct 2003 09:55:45 -0700 To: darwin-development@lists.apple.com Subject: Re: getaddrinfo bug The implementation of getaddrinfo in Mac OS X 10.2 was written to support our initial version of IPv6. It ended up getting used a lot more than we had expected. This was good news, in that it showed that there is a lot of code ready to take advantage of IPv6. We've done lots of work to improve IPv6 in 10.3. Included in that effort was an overhaul of getaddrinfo and getnameinfo. getaddrinfo no longer searches all sources for information (e.g. /etc/hosts + NetInfo + DNS). In 10.3 it follows lookupd's host search order and stops at the first "match". It's also faster and takes more advantage of local caching to gain better performance. -- Marc Majka _______________________________________________ darwin-development mailing list | darwin-development@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-development Do not post admin requests to the list. They will be ignored. ------ End of Forwarded Message

We can certainly determine the runtime OS version and use getaddrinfo() only if we are on Mac OS X 10.3 or later, and use gethostbyname() if we are on 10.1 and 10.2. Could one of you ask Apple to review this decision? Does anyone know what is the version of Darwin in Mac OS X 10.3? This is the output of the "uname -r" command.

uname -r returns: "7.0.0"

--> nspr

What I just got back from Apple on the subject... now i'm curious when this will get fixed. =) ------ Forwarded Message From: devbugs@apple.com Date: Tue, 21 Oct 2003 19:50:39 GMT Subject: Re: Bug ID #3454903: getaddrinfo lookup behavior is not the same as with gethostbyname Please include the line below in follow-up emails for this request. Follow-up: 2999907 Re: Bug ID #3454903: getaddrinfo lookup behavior is not the same as with gethostbyname Hello Jon, Thank you for taking the time to bring this issue to our attention. Engineering has reviewed your report and has determined that this is behavior intended by design and is working correctly per engineering specifications. Below, we have provided comments from engineering to help further explain this conclusion: >From your bug report, it sounds as if you were trying to block ads in a web browser by putting bogus entries in /etc/hosts. The Mac OS X 10.2 implementation of getaddrinfo consulted both /etc/hosts and DNS. This meant that the idea of blocking unwanted banner advertising by screening out unwanted hosts with bogus host entries in /etc/hosts did not work. The behavior of getaddrinfo changed in Mac OS X 10.3 so that it simply followed the lookupd host search order and stopped at the first entry. This means that in Mac OS X 10.3, one can block access to certain hosts with bogus hosts entries. We hope this information is helpful. Please do not hesitate to contact us should you wish to discuss this matter further. Thank you for your time and effort. Your help is greatly appreciated. Best Regards, Maurice Cusseaux Apple Developer Connection ******************************** For follow-ups please contact devbugs@apple.com

simple patch to disable getaddrinfo on OSX. this means that gethostbyname will be called instead, which at the moment it treated as non-threadsafe under OSX. this is not true for OSX 10.2 and above. so, i'm not entirely happy with this patch alone. i'm also not sure if OSX will return IPv6 addresses via gethostbyname. in which case this patch is definitely not good enough.

I think we want to use getaddrinfo on 10.3 (Darwin kernel 7.0) and higher. (10.3 has been released, in case you didn't know.) It's only 10.2 that has this problem, correct? Let's not hamstring future users. Ideally, Mozilla should automagically use gethostbyname on 10.0 - 10.2.x and getaddrinfo on 10.3 and up. That means a runtime initialization probe, I think. Perhaps too complicated. A better compile-time-oriented patch would do something like this: #if MACOS_DEPLOYMENT_TARGET < 100300 #define _PR_HAVE_GETHOSTBYNAME2 #else #define _PR_HAVE_GETADDRINFO #endif

ed: yes, i agree.. i'm not happy with the v1 patch either. i just put it up as an option.

A possible solution would be to use getipnodebyname instead of gethostbyname. It supports IPv6 and IPv4-mapped addresses, is thread safe, and supports the AI_ADDRCONFIG flag. See bug 68796 comment #43.

What we really need is a mechanism that specifically supports ad blocking. Besides people that are hacking their /etc/hosts files, is anyone else having a problem with this behavior? I've always disliked this user hacking of /etc/hosts. If we want to support ad blocking in this situation, can't we just decide to cancel the request for a hostname if the IP address is 0.0.0.0? I think this is network-incoherent, at least I've never seen any technical discussion that explains why an address is the whole IPv4 network should be allowed in /etc/hosts. TCP/Illustrated says that this cannot be a valid desintation address. I'm sure that is what people intend when they hack their /etc/hosts files, but do we want to encourage this behavior? Do we know other software will handle this bogus entry correctly?

Ha! the crux of the problem! =) It would be great to have a simple list that says: Hosts to block access to: It should be available via scripting as well so that outside applications can add/remove items from the list easily. Note that one benefit of using /etc/hosts over just having an application level blocking mechanism is that it works in all of the browsers that I use, not just Camino. So, maybe coming up with another central database that all browsers agree on using would be better. Until then /etc/hosts is gonna have to be that database. p.s...here is my list...=) it is amazing how much faster web pages load and how much **** i just don't see anymore...it almost making using a browser on a non-configured machine unbearable... 0.0.0.0 ar.atwola.com 0.0.0.0 ads.intuit.com 0.0.0.0 Garden.ngadcenter.net 0.0.0.0 Ogilvy.ngadcenter.net 0.0.0.0 ResponseMedia-ad.flycast.com 0.0.0.0 Suissa-ad.flycast.com 0.0.0.0 UGO.eu-adcenter.net 0.0.0.0 VNU.eu-adcenter.net 0.0.0.0 a32.g.a.yimg.com 0.0.0.0 ad-adex3.flycast.com 0.0.0.0 ad.adsmart.net 0.0.0.0 ad.ca.doubleclick.net 0.0.0.0 ad.de.doubleclick.net 0.0.0.0 ad.doubleclick.net 0.0.0.0 ad.fr.doubleclick.net 0.0.0.0 ad.jp.doubleclick.net 0.0.0.0 ad.linkexchange.com 0.0.0.0 ad.linksynergy.com 0.0.0.0 ad.nl.doubleclick.net 0.0.0.0 ad.no.doubleclick.net 0.0.0.0 ad.preferences.com 0.0.0.0 ad.sma.punto.net 0.0.0.0 ad.uk.doubleclick.net 0.0.0.0 ad.webprovider.com 0.0.0.0 ad08.focalink.com 0.0.0.0 adcontroller.unicast.com 0.0.0.0 adcreatives.imaginemedia.com 0.0.0.0 adex3.flycast.com 0.0.0.0 adforce.ads.imgis.com 0.0.0.0 adforce.imgis.com 0.0.0.0 adfu.blockstackers.com 0.0.0.0 adimage.blm.net 0.0.0.0 adimages.earthweb.com 0.0.0.0 adimg.egroups.com 0.0.0.0 admedia.xoom.com 0.0.0.0 adpick.switchboard.com 0.0.0.0 adremote.pathfinder.com 0.0.0.0 ads.admaximize.com 0.0.0.0 ads.bfast.com 0.0.0.0 ads.clickhouse.com 0.0.0.0 ads.enliven.com 0.0.0.0 ads.fairfax.com.au 0.0.0.0 ads.fool.com 0.0.0.0 ads.freshmeat.net 0.0.0.0 ads.hollywood.com 0.0.0.0 ads.i33.com 0.0.0.0 ads.infi.net 0.0.0.0 ads.jwtt3.com 0.0.0.0 ads.link4ads.com 0.0.0.0 ads.lycos.com 0.0.0.0 ads.madison.com 0.0.0.0 ads.mediaodyssey.com 0.0.0.0 ads.msn.com 0.0.0.0 ads.ninemsn.com.au 0.0.0.0 ads.seattletimes.com 0.0.0.0 ads.smartclicks.com 0.0.0.0 ads.smartclicks.net 0.0.0.0 ads.sptimes.com 0.0.0.0 ads.tripod.com 0.0.0.0 ads.web.aol.com 0.0.0.0 ads.x10.com 0.0.0.0 ads.xtra.co.nz 0.0.0.0 ads.zdnet.com 0.0.0.0 ads01.focalink.com 0.0.0.0 ads02.focalink.com 0.0.0.0 ads03.focalink.com 0.0.0.0 ads04.focalink.com 0.0.0.0 ads05.focalink.com 0.0.0.0 ads06.focalink.com 0.0.0.0 ads08.focalink.com 0.0.0.0 ads09.focalink.com 0.0.0.0 ads1.activeagent.at 0.0.0.0 ads10.focalink.com 0.0.0.0 ads11.focalink.com 0.0.0.0 ads12.focalink.com 0.0.0.0 ads14.focalink.com 0.0.0.0 ads16.focalink.com 0.0.0.0 ads17.focalink.com 0.0.0.0 ads18.focalink.com 0.0.0.0 ads19.focalink.com 0.0.0.0 ads2.zdnet.com 0.0.0.0 ads20.focalink.com 0.0.0.0 ads21.focalink.com 0.0.0.0 ads22.focalink.com 0.0.0.0 ads23.focalink.com 0.0.0.0 ads24.focalink.com 0.0.0.0 ads25.focalink.com 0.0.0.0 ads3.zdnet.com 0.0.0.0 ads5.gamecity.net 0.0.0.0 adserv.iafrica.com 0.0.0.0 adserv.quality-channel.de 0.0.0.0 adserver.dbusiness.com 0.0.0.0 adserver.garden.com 0.0.0.0 adserver.janes.com 0.0.0.0 adserver.merc.com 0.0.0.0 adserver.monster.com 0.0.0.0 adserver.track-star.com 0.0.0.0 adserver1.ogilvy-interactive.de 0.0.0.0 adtegrity.spinbox.net 0.0.0.0 antfarm-ad.flycast.com 0.0.0.0 au.ads.link4ads.com 0.0.0.0 banner.media-system.de 0.0.0.0 banner.orb.net 0.0.0.0 banner.relcom.ru 0.0.0.0 banners.easydns.com 0.0.0.0 banners.looksmart.com 0.0.0.0 banners.wunderground.com 0.0.0.0 barnesandnoble.bfast.com 0.0.0.0 beseenad.looksmart.com 0.0.0.0 bizad.nikkeibp.co.jp 0.0.0.0 bn.bfast.com 0.0.0.0 c3.xxxcounter.com 0.0.0.0 califia.imaginemedia.com 0.0.0.0 cds.mediaplex.com 0.0.0.0 click.avenuea.com 0.0.0.0 click.go2net.com 0.0.0.0 click.linksynergy.com 0.0.0.0 cookies.cmpnet.com 0.0.0.0 cornflakes.pathfinder.com 0.0.0.0 counter.hitbox.com 0.0.0.0 crux.songline.com 0.0.0.0 erie.smartage.com 0.0.0.0 etad.telegraph.co.uk 0.0.0.0 fp.valueclick.com 0.0.0.0 gadgeteer.pdamart.com 0.0.0.0 gm.preferences.com 0.0.0.0 gp.dejanews.com 0.0.0.0 hg1.hitbox.com 0.0.0.0 image.click2net.com 0.0.0.0 image.eimg.com 0.0.0.0 images2.nytimes.com 0.0.0.0 jobkeys.ngadcenter.net 0.0.0.0 kansas.valueclick.com 0.0.0.0 leader.linkexchange.com 0.0.0.0 liquidad.narrowcastmedia.com 0.0.0.0 ln.doubleclick.net 0.0.0.0 m.doubleclick.net 0.0.0.0 macaddictads.snv.futurenet.com 0.0.0.0 maximumpcads.imaginemedia.com 0.0.0.0 media.preferences.com 0.0.0.0 mercury.rmuk.co.uk 0.0.0.0 mojofarm.sjc.mediaplex.com 0.0.0.0 nbc.adbureau.net 0.0.0.0 newads.cmpnet.com 0.0.0.0 ng3.ads.warnerbros.com 0.0.0.0 ngads.smartage.com 0.0.0.0 nsads.hotwired.com 0.0.0.0 ntbanner.digitalriver.com 0.0.0.0 ph-ad05.focalink.com 0.0.0.0 ph-ad07.focalink.com 0.0.0.0 ph-ad16.focalink.com 0.0.0.0 ph-ad17.focalink.com 0.0.0.0 ph-ad18.focalink.com 0.0.0.0 rd.yahoo.com 0.0.0.0 realads.realmedia.com 0.0.0.0 redherring.ngadcenter.net 0.0.0.0 redirect.click2net.com 0.0.0.0 regio.adlink.de 0.0.0.0 retaildirect.realmedia.com 0.0.0.0 s2.focalink.com 0.0.0.0 sh4sure-images.adbureau.net 0.0.0.0 spin.spinbox.net 0.0.0.0 static.admaximize.com 0.0.0.0 stats.superstats.com 0.0.0.0 sview.avenuea.com 0.0.0.0 thinknyc.eu-adcenter.net 0.0.0.0 tracker.clicktrade.com 0.0.0.0 tsms-ad.tsms.com 0.0.0.0 v0.extreme-dm.com 0.0.0.0 v1.extreme-dm.com 0.0.0.0 van.ads.link4ads.com 0.0.0.0 view.accendo.com 0.0.0.0 view.avenuea.com 0.0.0.0 w113.hitbox.com 0.0.0.0 w25.hitbox.com 0.0.0.0 web2.deja.com 0.0.0.0 webads.bizservers.com 0.0.0.0 www.PostMasterBannerNet.com 0.0.0.0 www.ad-up.com 0.0.0.0 www.admex.com 0.0.0.0 www.alladvantage.com 0.0.0.0 www.burstnet.com 0.0.0.0 www.commission-junction.com 0.0.0.0 www.eads.com 0.0.0.0 www.freestats.com 0.0.0.0 www.imaginemedia.com 0.0.0.0 www.netdirect.nl 0.0.0.0 www.oneandonlynetwork.com 0.0.0.0 www.targetshop.com 0.0.0.0 www.teknosurf2.com 0.0.0.0 www.teknosurf3.com 0.0.0.0 www.valueclick.com 0.0.0.0 www.websitefinancing.com 0.0.0.0 www2.burstnet.com 0.0.0.0 www4.trix.net 0.0.0.0 www80.valueclick.com 0.0.0.0 z.extreme-dm.com 0.0.0.0 z0.extreme-dm.com 0.0.0.0 z1.extreme-dm.com 0.0.0.0 spinbox.versiontracker.com 0.0.0.0 netadsrv.iworld.com 0.0.0.0 ads.admonitor.net 0.0.0.0 ads.imaginemedia.com 0.0.0.0 advertising.com 0.0.0.0 kermit.macnn.com 0.0.0.0 servedby.advertising.com 0.0.0.0 ads.tucows.com 0.0.0.0 service.bfast.com 0.0.0.0 vsii.spinbox.net 0.0.0.0 ds.sf.futurenet.com 0.0.0.0 adserver.bizland-inc.net 0.0.0.0 ads4.earthweb.com 0.0.0.0 www.sponsorships.net 0.0.0.0 spinbox.macpublishing.net 0.0.0.0 www.adtagger.com 0.0.0.0 adcreatives.radcity.net 0.0.0.0 sponsors.waveshift.com 0.0.0.0 ad.au.doubleclick.net 0.0.0.0 ads.intelihealth.com 0.0.0.0 oz.valueclick.com 0.0.0.0 banner.linkexchange.com 0.0.0.0 ads.adflight.com 0.0.0.0 ads.applelinks.com 0.0.0.0 adsrv.ilife.com 0.0.0.0 iv.doubleclick.net 0.0.0.0 images.go2net.com 0.0.0.0 connect.247media.ads.link4ads.com 0.0.0.0 links.quinstreet.com 0.0.0.0 adserver.ads360.com 0.0.0.0 www.1blink.com 0.0.0.0 banners.freeware.ru 0.0.0.0 a.tribalfusion.com 0.0.0.0 ads.eudora.com 0.0.0.0 ads2.eudora.com 0.0.0.0 www.qksrv.net 0.0.0.0 spinbox.techtracker.com 0.0.0.0 ads.uniquemedia.net 0.0.0.0 ads-e.focalink.com 0.0.0.0 littlebuddy.apple.com 0.0.0.0 server2.as5000.com 0.0.0.0 adserver1.backbeatmedia.com 0.0.0.0 tracker.tradedoubler.com 0.0.0.0 us.a1.yimg.com 0.0.0.0 ads1.ad-flow.com 0.0.0.0 ads.quicken.com 0.0.0.0 fl01.ct2.comclick.com 0.0.0.0 adserv.sapo.pt 0.0.0.0 mjxads.internet.com 0.0.0.0 ads.businessweek.com 0.0.0.0 ads.dealnews.com 0.0.0.0 ads.courier-journal.com 0.0.0.0 www.whitehouse.com 0.0.0.0 www.actinxxx.com 0.0.0.0 www.adultfilmarchive.com 0.0.0.0 www.ainews.com 0.0.0.0 www.avn.com 0.0.0.0 www.barefacts.com 0.0.0.0 www.eroticmoviecompendium.com 0.0.0.0 www.iafd.com 0.0.0.0 www.lukeford.com 0.0.0.0 www.rame.net 0.0.0.0 www.sextracker.com 0.0.0.0 www.escapade.nl 0.0.0.0 www.sexhound.com 0.0.0.0 the.sextracker.com 0.0.0.0 outlawedjapan.com 0.0.0.0 www.bestamateur.com 0.0.0.0 www.cumqueenkari.com 0.0.0.0 www.virtuagirl.com 0.0.0.0 www.thumbnetwork.com 0.0.0.0 www.max-productions.com 0.0.0.0 www.smutserver.com 0.0.0.0 www.yahan.com 0.0.0.0 www.vixenvideos.com 0.0.0.0 www.wantonwife.com 0.0.0.0 www4.smutserver.com 0.0.0.0 www.suzi-wong.com 0.0.0.0 www.100freexxxpics.com 0.0.0.0 www.creamypies.com 0.0.0.0 www.cumshotfantasies.com 0.0.0.0 www.gigme.com 0.0.0.0 www.terra.es 0.0.0.0 pornstars.eroticism.com 0.0.0.0 samples.celebclub.com 0.0.0.0 www.girls4guys.com 0.0.0.0 www.hardandfast.com 0.0.0.0 programs.amateurpages.com 0.0.0.0 www.kostenlosecams.de 0.0.0.0 www.cumexcite.com 0.0.0.0 maya21.myifriends.net 0.0.0.0 www.algonet.se 0.0.0.0 www.freesextgp.com 0.0.0.0 www.thumbshack.com 0.0.0.0 www.amateurfreehost.com 0.0.0.0 www.sextext.com 0.0.0.0 sextracker.com 0.0.0.0 www.stickyfist.com 0.0.0.0 www.eros-island.com 0.0.0.0 smutserver.com 0.0.0.0 www.pussyfiend.com 0.0.0.0 www.ispyceleb.com 0.0.0.0 www3.smutserver.com 0.0.0.0 www2.smutserver.com 0.0.0.0 www.just-raw-sex.com 0.0.0.0 www.thehun.com 0.0.0.0 ads.specificpop.com 0.0.0.0 ads.osdn.com 0.0.0.0 ads.as4x.tmcs.net 0.0.0.0 z1.adserver.com 0.0.0.0 1.marketbanker.com 0.0.0.0 www.marketbanker.com 0.0.0.0 pagead2.googlesyndication.com 0.0.0.0 graphics7.nytimes.com 0.0.0.0 a.as-us.falkag.net 0.0.0.0 netshelter.adtrix.com 0.0.0.0 pr.atwola.com 0.0.0.0 www.timeinc.net 0.0.0.0 rmedia.boston.com 0.0.0.0 statse.webtrendslive.com

revised patch. wtc noted that _darwin.h needs to enable _PR_INET6_PROBE for target platforms less than 10.3 not less than 10.2.

Looks pretty good, Darin. Forgive the following newbie questions: What is the current value of MACOS_DEPLOYMENT_TARGET and how is its value assigned/determined? Will the runtime check you've added in the patch to ptio.c be done just once or will that code be run with every connection made?

MACOS_DEPLOYMENT_TARGET is set by NSPR's configure script. there is an argument that can be passed to NSPR's configure script to alter the value. the default value appears to be 10.1. this runtime check will only happen once at startup.

Comment on attachment 136390 [details] [diff] [review] v2.1 patch r=wtc. I like this patch!

Comment on attachment 136390 [details] [diff] [review] v2.1 patch would be good to get this in for beta.

fixed on NSPR trunk and NSPRPUB_4_2_CLIENT_BRANCH. this fix will appear in mozilla 1.6 beta.

sadly, i'm on 10.3 now so this issue doesn't bug me personally anymore, but thank you for fixing this! i think all the 10.2.x people will be eternally grateful and it is the right thing to do anyway. another satisified customer. =)

VERIFIED: fixed. Added a 0.0.0.0 entry to /etc/hosts. Correct behavior would be to block hostname. Mozilla 1.6a - incorrect behavior. Mozilla 1.6f - correct behavior.