We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Əgər kömək lazımdırsa lütfən yeni sual verin.

Does the latest version of firefox (44.0) have a problem storing cookies where the name of the cookie contains a space?

  • 4 cavab
  • 1 has this problem
  • 1 view
  • Last reply by Kohei

pizzle1983
pizzle1983
more options

Hi,

I have javascript code that is run to create certain cookies. Since updating to Firefox 44.0, it would seem cookies don't get stored if their name contains a space.

Cookie that does not get created anymore (space inbetween 'Full' and 'text': document.cookie="text_searchfield_ROW0LIBRIOS2SEARCHFIELD[Full text]=england; path=/";

There's a space because these names have to be generated dynamically.

This is causing a bit of stress as there's a lot of websites dependent on this.

Any feedback would be appreciated.

Adam.

Hi, I have javascript code that is run to create certain cookies. Since updating to Firefox 44.0, it would seem cookies don't get stored if their name contains a space. Cookie that does not get created anymore (space inbetween 'Full' and 'text': document.cookie="text_searchfield_ROW0LIBRIOS2SEARCHFIELD[Full text]=england; path=/"; There's a space because these names have to be generated dynamically. This is causing a bit of stress as there's a lot of websites dependent on this. Any feedback would be appreciated. Adam.

Chosen solution

I have posted the site compatibility doc: https://www.fxsitecompat.com/en-CA/docs/2016/whitespaces-are-no-longer-allowed-in-cookie-names/

Yeah, some apps might be broken due to this change. Mozilla developers are now aware of the issue, and Firefox may allow spaces again for backward compatibility.

Read this answer in context 👍 1

All Replies (4)

pizzle1983
pizzle1983 Question owner
more options

Maybe forget the bit about 'causing a bit of stress'. The code has been updated affecting my sites.

Definitely want to make you aware in case though.

Kohei
Kohei
more options

Perhaps this is a regression from a cookie-related security issue fixed with Firefox 44. But, I believe you have to encode the value anyway before being saved, because white spaces are not allowed. See https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie

Filed a bug to make sure this change is intentional.

Modified by Kohei

pizzle1983
pizzle1983 Question owner
more options

Thanks for the response Kohei.

I agree, we should have been encoding these names - we just didn't realise we weren't encoding them until version 44 stopped them from working.

I'm sure there'll be a few others getting caught out with this.

Thank you for you time.

Kohei
Kohei
more options

Seçilmiş Həll

I have posted the site compatibility doc: https://www.fxsitecompat.com/en-CA/docs/2016/whitespaces-are-no-longer-allowed-in-cookie-names/

Yeah, some apps might be broken due to this change. Mozilla developers are now aware of the issue, and Firefox may allow spaces again for backward compatibility.