Cisco's Website down?

2004-03-15 Thread joej
Anyone else seeing an error getting to www.cisco.com? !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN HTMLHEAD TITLE403 Forbidden/TITLE /HEADBODY H1Forbidden/H1 You don't have permission to access / on this server.P PAdditionally, a 403 Forbidden error was encountered while trying to use an

Re: Cisco's Website down?

2004-03-15 Thread Brian Bruns
On Mon, March 15, 2004 3:21 pm, [EMAIL PROTECTED] said: Anyone else seeing an error getting to www.cisco.com? Yep, from AOL, level3, and RoadRunner. All coming back as 403. -- Brian Bruns The Summit Open Source Development Group Open Solutions For A Closed World / Anti-Spam Resources

Re: Cisco's Website down?

2004-03-15 Thread Adi Linden
Anyone else seeing an error getting to www.cisco.com? Maybe I missed to renew a service contract? They don't like me either. Adi

Re: Cisco's Website down?

2004-03-15 Thread William Warren
no issues here [EMAIL PROTECTED] wrote: Anyone else seeing an error getting to www.cisco.com? !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN HTMLHEAD TITLE403 Forbidden/TITLE /HEADBODY H1Forbidden/H1 You don't have permission to access / on this server.P PAdditionally, a 403 Forbidden error was

Re: Cisco's Website down?

2004-03-15 Thread Rachael Treu
Nor here. Been connected via GBLX all day to one of their pages. ymmv, --ra On Mon, Mar 15, 2004 at 03:42:12PM -0500, William Warren said something to the effect of: no issues here [EMAIL PROTECTED] wrote: Anyone else seeing an error getting to www.cisco.com? !DOCTYPE HTML

Re: Cisco's Website down?

2004-03-15 Thread Stephen J. Wilcox
Anyone else seeing an error getting to www.cisco.com? Yep, from AOL, level3, and RoadRunner. All coming back as 403. You expected the webserver to react differently depending on how your packets got there? Steve

Re: Cisco's Website down?

2004-03-15 Thread Brian Bruns
On Monday, March 15, 2004 6:01 PM [EST], Stephen J. Wilcox [EMAIL PROTECTED] wrote: Anyone else seeing an error getting to www.cisco.com? Yep, from AOL, level3, and RoadRunner. All coming back as 403. You expected the webserver to react differently depending on how your packets got there?