- From: Duen-wen Hsiao <edvwkh@hotmail.com>
- Date: Sat, 12 Sep 2009 09:15:14 -0500
- To: <ot@w3.org>, <www-validator@w3.org>
- Message-ID: <COL120-W10AD3664E1E3B009A61A3DCCE60@phx.gbl>
Good day, We got a server that's serving webpages for our students. The server's address is COIS-linux.austincc.edu. We were able to do the html validation against validator.w3.org but we weren't able to do the ccs validation against jigsaw.w3.org The error message is Target: http://cois-linux.austincc.edu/~yost3575830/ I/O Error: Unable to contact target server cois-linux.austincc.edu:80 after 3 tries. We were able to do the validation against both server before. Here is what I found out. On cois-linux.austincc.edu, the ping against jigsaw.w3.org failed. COIS-Linux:/ # ping jigsaw.w3.org PING jigsaw.w3.org (128.30.52.72) 56(84) bytes of data. --- jigsaw.w3.org ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2009ms The traceroute ended at trantor.haven.csail.mit.edu. COIS-Linux:/ # traceroute jigsaw.w3.org traceroute to jigsaw.w3.org (128.30.52.72), 30 hops max, 40 byte packets 1 aus-thenet-core-ge-0-1-0-11.the.net (129.117.37.113) 7.417 ms 5.432 ms 5.558 ms 2 aust-utnoc-core-ge-6-0-0-2.tx-bb.net (192.12.10.109) 5.592 ms 6.691 ms 6.250 ms 3 dlls-lvl3-core-ge-2-0-0-1-v741.tx-bb.net (192.124.227.34) 14.014 ms 14.208 ms 13.473 ms 4 dlls-lvl3-isp-vlan710.tx-bb.net (192.124.227.74) 7.051 ms 6.726 ms 6.869 ms 5 xe-9-3-0.edge3.Dallas1.Level3.net (4.79.182.245) 6.945 ms 6.212 ms 6.633 ms 6 ae-82-80.ebr2.Dallas1.Level3.net (4.69.145.179) 13.693 ms ae-72-70.ebr2.Dallas1.Level3.net (4.69.145.115) 10.869 ms ae-82-80.ebr2.Dallas1.Level3.net (4.69.145.179) 9.957 ms 7 ae-3.ebr4.NewYork1.Level3.net (4.69.137.122) 42.036 ms 41.653 ms 50.545 ms 8 ae-74-74.csw2.NewYork1.Level3.net (4.69.134.118) 48.631 ms ae-84-84.csw3.NewYork1.Level3.net (4.69.134.122) 41.782 ms ae-94-94.csw4.NewYork1.Level3.net (4.69.134.126) 44.200 ms 9 ae-61-61.ebr1.NewYork1.Level3.net (4.69.134.65) 42.783 ms ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 42.516 ms ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) 42.514 ms 10 * * * 11 * * * 12 ae-7-7.car1.Boston1.Level3.net (4.69.132.241) 73.494 ms 69.682 ms 67.185 ms 13 MASSACHUSET.car1.Boston1.Level3.net (4.53.48.98) 47.123 ms 47.394 ms 45.968 ms 14 B24-RTR-2-BACKBONE.MIT.EDU (18.168.0.23) 47.419 ms 49.229 ms 47.812 ms 15 MITNET.TRANTOR.CSAIL.MIT.EDU (18.4.7.65) 47.752 ms 48.158 ms 46.905 ms 16 trantor.haven.csail.mit.edu (128.30.0.254) 47.429 ms 47.142 ms 47.461 ms 17 * * * .... While on other machines, I was able to ping and the traceroute return successful quasar:~ # traceroute jigsaw.w3.org traceroute to jigsaw.w3.org (128.30.52.72), 30 hops max, 40 byte packets 1 10.44.0.2 (10.44.0.2) 0.323 ms 0.274 ms 0.276 ms 2 10.0.41.1 (10.0.41.1) 0.781 ms 0.708 ms 0.804 ms 3 aus-thenet-core-ge-0-1-0-11.the.net (129.117.37.113) 1.495 ms 1.789 ms 1.595 ms 4 aust-utnoc-core-ge-6-0-0-2.tx-bb.net (192.12.10.109) 1.274 ms 1.231 ms 1.177 ms 5 dlls-lvl3-core-ge-2-0-0-1-v741.tx-bb.net (192.124.227.34) 6.118 ms 5.939 ms 5.914 ms 6 dlls-lvl3-isp-vlan710.tx-bb.net (192.124.227.74) 6.638 ms 6.692 ms 6.723 ms 7 xe-9-3-0.edge3.Dallas1.Level3.net (4.79.182.245) 6.719 ms 6.769 ms 6.399 ms 8 ae-82-80.ebr2.Dallas1.Level3.net (4.69.145.179) 9.587 ms ae-62-60.ebr2.Dallas1.Level3.net (4.69.145.51) 9.258 ms ae-82-80.ebr2.Dallas1.Level3.net (4.69.145.179) 7.290 ms 9 ae-3.ebr4.NewYork1.Level3.net (4.69.137.122) 44.018 ms 43.037 ms 41.515 ms 10 ae-94-94.csw4.NewYork1.Level3.net (4.69.134.126) 41.329 ms ae-64-64.csw1.NewYork1.Level3.net (4.69.134.114) 43.125 ms ae-94-94.csw4.NewYork1.Level3.net (4.69.134.126) 52.794 ms 11 ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) 41.800 ms 42.275 ms ae-61-61.ebr1.NewYork1.Level3.net (4.69.134.65) 41.696 ms 12 ae-1-8.bar2.Boston1.Level3.net (4.69.140.97) 46.552 ms 46.920 ms 46.620 ms 13 * * * 14 ae-7-7.car1.Boston1.Level3.net (4.69.132.241) 63.396 ms 63.084 ms 61.930 ms 15 MASSACHUSET.car1.Boston1.Level3.net (4.53.48.98) 47.228 ms 46.710 ms 46.618 ms 16 B24-RTR-2-BACKBONE-2.MIT.EDU (18.168.1.23) 46.851 ms 47.044 ms 47.036 ms 17 MITNET.TRANTOR.CSAIL.MIT.EDU (18.4.7.65) 46.964 ms 47.623 ms 46.691 ms 18 trantor.haven.csail.mit.edu (128.30.0.254) 47.164 ms 47.219 ms 46.683 ms 19 dr-nick.w3.org (128.30.52.72) 47.063 ms 47.331 ms 47.179 ms the traceroute against validator on COIS-linux.austincc.edu was also successful COIS-Linux:/ # traceroute validator.w3.org traceroute to validator.w3.org (128.30.52.70), 30 hops max, 40 byte packets 1 aus-thenet-core-ge-0-1-0-11.the.net (129.117.37.113) 5.842 ms 6.529 ms 5.659 ms 2 aust-utnoc-core-ge-6-0-0-2.tx-bb.net (192.12.10.109) 4.727 ms 3.795 ms 3.611 ms 3 dlls-lvl3-core-ge-2-0-0-1-v741.tx-bb.net (192.124.227.34) 9.267 ms 9.275 ms 9.173 ms 4 dlls-lvl3-isp-vlan710.tx-bb.net (192.124.227.74) 86.836 ms 85.341 ms 81.215 ms 5 xe-9-3-0.edge3.Dallas1.Level3.net (4.79.182.245) 10.046 ms 12.044 ms 11.994 ms 6 ae-92-90.ebr2.Dallas1.Level3.net (4.69.145.243) 15.479 ms ae-62-60.ebr2.Dallas1.Level3.net (4.69.145.51) 10.909 ms ae-82-80.ebr2.Dallas1.Level3.net (4.69.145.179) 10.855 ms 7 * ae-3.ebr4.NewYork1.Level3.net (4.69.137.122) 55.284 ms 52.304 ms 8 ae-74-74.csw2.NewYork1.Level3.net (4.69.134.118) 54.329 ms ae-84-84.csw3.NewYork1.Level3.net (4.69.134.122) 51.999 ms ae-94-94.csw4.NewYork1.Level3.net (4.69.134.126) 59.974 ms 9 ae-61-61.ebr1.NewYork1.Level3.net (4.69.134.65) 49.059 ms ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 47.999 ms ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) 47.673 ms 10 * * * 11 ae-0-11.bar1.Boston1.Level3.net (4.69.140.89) 55.169 ms 52.933 ms 54.446 ms 12 ae-7-7.car1.Boston1.Level3.net (4.69.132.241) 53.582 ms 53.361 ms 52.963 ms 13 MASSACHUSET.car1.Boston1.Level3.net (4.53.48.98) 47.755 ms 47.402 ms 47.528 ms 14 B24-RTR-2-BACKBONE.MIT.EDU (18.168.0.23) 47.971 ms 48.231 ms 47.329 ms 15 MITNET.TRANTOR.CSAIL.MIT.EDU (18.4.7.65) 47.497 ms 47.156 ms 47.518 ms 16 trantor.haven.csail.mit.edu (128.30.0.254) 47.978 ms 47.748 ms 51.978 ms 17 krusty.w3.org (128.30.52.70) 48.280 ms 46.816 ms 46.945 ms So I was thinking perhaps COIS-linux.austincc.edu is blocked by jigsaw.w3.org? Would you please kindly check? Thanks. Duen-wen Hsiao > CC: www-validator@w3.org > From: ot@w3.org > To: edvwkh@hotmail.com > Subject: Re: w3c validator with authtype = digest > Date: Tue, 27 Jan 2009 09:12:29 -0500 > > Hello, > > On 26-Jan-09, at 9:12 PM, Duen-wen Hsiao wrote: > > I have a question for you. One of our instructors is using w3c > > validator for her classes. However, we are using authtype = digest > > instead of basic for authentication for each individual student's > > webpages. And looks like the w3c validator does not work. > > Yes, unfortunately, due to the way digest authentication works, there > is no way (or rather I should say, none known to us) we could have the > validator proxy the authentication for digest-auth protected > resources. See ramblings on the topic here: > http://lists.w3.org/Archives/Public/public-qa-dev/2007Feb/0000.html > > One solution I could think of would be to install the validator on > your internal network and then set up your web server to not require > authentication for that particular host/IP. > > Hope this helps, > olivier > -- > olivier Thereaux - W3C Open Source Software : http://www.w3.org/Status > Do you ♥ Validators? > Donate or become a Sponsor: http://www.w3.org/QA/Tools/Donate > _________________________________________________________________ Bing brings you health info from trusted sources. http://www.bing.com/search?q=pet+allergy&form=MHEINA&publ=WLHMTAG&crea=TXT_MHEINA_Health_Health_PetAllergy_1x1
Received on Saturday, 12 September 2009 14:18:56 UTC