youtube-nocookie domain has problems in Firefox, but not in Google Chrome


I post the link to my problem report, youtube-nocookie domain has problems in Firefox, but not in Google Chrome,  because I use the “youtube-nocookie” domain when I embed YouTube videos in this blog.  I do that at the suggestion of YouTube because I presume that avoids putting cookies on your computer when you watch the video.  That presumption may be false, but that is a matter for another post.

I have reported the problem to Mozilla the owners of Firefox.  It seems that Mozilla and YouTube just point the finger at each other.  Since the problem is as yet unsolved, I gave you the link so you can follow the back and forth until the problem gets resolved.  You may also find this entertaining and educational if you have experienced this problem on your own, and have been wondering what the issue is.

I have also replied to a YouTube support forum question.  I have had a response from someone who wants to look into the problem.


March 9, 2015

My Final response is https://productforums.google.com/d/msg/youtube/6JmM2mr_r10/Cr4L0HvM1McJ

I should have pointed out that the file http://www.youtube.com/watch?v=TLT2nV3sWtw does exist, but the file http://www.youtube-nocookie.com/watch?v=TLT2nV3sWtw does not. The file is on the www.youtube.com server but not on the www.youtube-nocookie.com. You’d think that would be an easy oversight to fix. You wouldn’t think it would take YouTube this long to notice the problem, or that I would have to be the one to point it out. I think YouTube should send me a cookie for finding the problem for them 🙂

If you click on the link of the file that doesn’t exist, it appears to be blank. If your browser shows URL titles in tabs, then you will see the title “404 file not found.” You have to be wide awake to notice that this is how YouTube is trying to deliver the message to you. Would you normally look to the title of the file that surprisingly shows up empty?

Remember, this is a problem that shows up in Firefox and some other browsers, but not in all browsers.

The file that does not exist, does not exist for all browsers. The issue is that YouTube only tries to use the non-existent file for some browsers. So it is not the browser’s fault that YouTube does this to them.

I found out exactly how YouTube screws things up for other browsers. When I insert a YouTube video in this blog, I use code that accesses a file like https://www.youtube-nocookie.com/embed/TLT2nV3sWtw in an iframe.

When YouTube constructs the contents of the iframe for Firefox, it sets up a video player and gives the player the URL https://www.youtube-nocookie.com/watch?feature=player_embedded&v=TLT2nV3sWtw. When YouTube sets up the same player in the Google Chrome browser, it give the player the URL https://www.youtube.com/watch?v=TLT2nV3sWtw. It is smart enough to take out the “-nocookie” in the domain name. In other words when it sets up Google Chrome, it gives it a URL that exists. When YouTube (owned by Google) sets up Firefox, it gives it a URL that it knows does not exist.

Of course Google wouldn’t sabotage browsers from other companies. It just made sure that the setup worked for its own browser, and didn’t bother to do the same for the other browsers. I am sure it was just an oversight. Google’s motto is “Do no harm”, right?


March 11, 2015

There is now a reply on the Google Product forums.

ytcrschmidt 9:36 AM (50 minutes ago)

Hi all,

YouTube developers are aware of the problem, and are working on a solution. I apologize for the inconvenience.


March 12, 2015

I have verified that YouTube has fixed the problem. I checked one of the many videos that requests no cookies be used and it is now playing again.

However, if you click on the YouTube icon at the bottom right corner of the video, you still do not get to a working version of the video on YouTube. You get what looks like a blank page. The title of that blank page is “404 Not Found”. Google developers are still working to fix that and whatever other problems continue to lurk.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.