6 Users Commented In This Post

Subscribe To This Post Comment Rss Or TrackBack URL
netking says:

An other alternative would be to install google browser sync extension.

This extension stores all your firefox related stuff like cookies, saved passwords, cache, history on google servers… The only sync it doesn’t store is your local settings (extensions).

This is really practical, as you just have to install the extension to “feel at home” on any Firefox, just by installing the extension.

You have to have a google account to use this and if your concerned about privacy with Google storing personal data, just skip the tip !

Martin says:

I suppose this is only working with firefox settings ? Nice idea though, will be taking a look at it soon.

Thanks for all your tips and recommendations, they are really valuable to me..

Nathan says:

Well, if you install FF for the first time, you are prompted to transfer your settings: cookies, bookmarks, etc. So, I guess you could reinstall firefox or delete your current profile/reinstall to import everything automatically.

Frank Huber says:

I could not migrate my cookies from IE5.5 to FF2.0, even though I did everything according to Martin’s recipe. The cookies.txt file exported from IE contained hex 0D 0A 0D 0A (CR LF CR LF) between every pair of lines, and my text editor (Kedit) retained that structure.

I placed a “.” before each cookie description that didn’t start with “www.” and deleted a few descriptions for cookies that I no longer wanted.

I had just installed FF 2.0, and had used it only once (to search for how to migrate my cookies), so I renamed the existing cookies.txt as cookies.jnk and copied the edited cookie file to my profile folder.

The upshot: No cookies are visible to FF.

P.S.: Nathan, FF 2.0 did NOT prompt me to transfer my cookies, only my bookmarks.

Martin says:

Frank I only tested it with IE 6.0 and that browser did not add hex values to the cookies.txt file.

Frank Huber says:

I guess I confused everyone by using 0D for CR and 0A for LF = line feed = newline code. I should’ve said that most DOS-oriented editors (like Kedit) default to terminating each line with a carriage return AND a line feed.

After posting, I examined Firefox’s cookie.txt file and saw only line feeds (newline codes to Unixheads ;) ). Also, I saw tabs representing whitespace.

Once I told my editor to output only line feeds — and just to be sure, I also told it to output all whitespace as tabs — Firefox accepted my edited cookie.txt file as if it was its own child. Success! Thanks, Martin, for getting me started.

Leave Your Comments Below
Hello, please leave your thought below

Please Note: Each comment will be manually approved by an admin. There is no guarantee that a comment will be posted. Please do not submit the comment multiple times.