Page 1 of 1

receiving 404s from tutorial links

Posted: Sun Aug 21, 2011 11:36 pm
by theelemur
I get this response:

"Woah there, Turbo!
Our server gnomes couldn't find the page you are looking for.
Seriously, where are you trying to go?"

when attempting to follow the following links:
http://www.sparkfun.com/tutorials/57
http://www.sparkfun.com/tutorials/148
..etc

looks like the tutorial links are failing for me.

Re: receiving 404s from tutorial links

Posted: Mon Aug 22, 2011 6:40 am
by phalanx
It may have been a temporary issue because the links are working fine for me.

-Bill

Re: receiving 404s from tutorial links

Posted: Wed Aug 24, 2011 5:59 pm
by Chanler
I came here with the same question too. Not sure when or if they've worked for me before.

Firefox 5 on Ubuntu, if that helps any.

Re: receiving 404s from tutorial links

Posted: Wed Aug 24, 2011 6:07 pm
by phalanx
And they are still working for me with IE and Firefox on a few different computers.

-Bill

Re: receiving 404s from tutorial links

Posted: Sat Sep 10, 2011 8:00 am
by pmscientist
Are you using the HTTPS Everywhere plugin? If so, try disabling the Sparkfun rule for HTTPS Everywhere. I was having this same issue with both news and tutorial pages, that fixed it for me.

SF: Looks to me like the majority of content from sparkfun.com does get encrypted successfully when using HTTPS Everywhere. Based on a packet capture, when making a request for a news page there is a handful of encrypted traffic, and then an unencrypted GET for /news/view, which is what appears to cause the 404. Not sure where that URL came from, as don't see it in the page source, and the preceding packets are encrypted. It works totally fine when I disable the HTTPS Everywhere rule, though I still don't see a reference to /news/view in the page source. Hopefully that helps. It would be nice to use HTTPS Everywhere, but the important parts are encrypted, so no big deal to me.

Re: receiving 404s from tutorial links

Posted: Wed Sep 21, 2011 8:54 pm
by Chanler
Thanks pmscientist. Disabling HTTPS Everywhere worked.