Description of problem:
It is possible for a user to see a 404 if they do not have the correct settings
in their browser.  For instance, if I create a multi-lingual item in three
languages: French, German, and Spanish and my browser only has English under the
"Edit -> preferences -> Languages" then going to the url
(/ccm/content/myfolder/my-multi-lingual-item) will give a 404.  However, if I
add any of the three appropriate languages to my browser and then reload the
page then the item will load.

I propose that, if the user does not have a language in their header that
matches an available language, the system should server the item using the
default language for the Content Bundle instead of giving a 404.  


Version-Release number of selected component (if applicable):
Nightly

How reproducible:
Always

Steps to Reproduce:
1.  Create a content item and make the primary instance use a language that is
not in your language preferences.
2.  Load the page and get the 404.
3.  Add the language to your preference and reload the page and you will see you
 no longer get the 404.
    
Actual results:
404

Expected results:
default content item

Additional info:
This will need to be fixed for Carrefour by the end of August...it would be nice
to have an official engineering solution rather than a one off solution.