Chrome “clear cookies on exit” feature does not work

Re:Chrome “clear cookies on exit” feature does not work by stevekemp on Sunday March 24, 2019 @07:56AM (#19475827)

I use firefox, and find this function useful:

     # Open a new firefox instance, with a temporary profile
     function firefox_temp() {
        dir=$(mktemp -d)
        echo "Profile directory: ${dir}"
        firefox --new-instance --profile ${dir}
        echo "Cleaning up .."
        rm -rf ${dir}
     }

I'm not familiar with Chrome, but perhaps there is a similar "profile-directory" argument you can point to a temporary location?

[ Parent | on HN ]

Re:Chrome “clear cookies on exit” feature does not work by josephorjoe on Sunday March 24, 2019 @09:08AM (#19476117)

You can use the `--user-data-dir` arg to specify a profile location when opening chrome. So, on a mac, something like:

  open -Fna /Applications/Google\ Chrome.app \
  --args --user-data-dir=/my_temp_profile_dir/my_tmp_profile

If you copy an existing profile to `my_tmp_profile` chrome will use that, otherwise it behaves like a new setup.

[ Parent | on HN ]

Re:Chrome “clear cookies on exit” feature does not work by Ysx on Sunday March 24, 2019 @08:55AM (#19476066)

That's interesting... does it behave much differently to private windows?

[ Parent | on HN ]

Re:Chrome “clear cookies on exit” feature does not work by stevekemp on Sunday March 24, 2019 @01:24PM (#19477508)

If we assume that the private-mode is "secure", then I suspect there's probably not a huge difference in practice.

But this way I'm very certain extensions, history, local-storage, etc, are absolutely not available.

(To be honest I tend to use this mostly avoid caching, and other things. Useful when you're testing redirects and new designs.)

[ Parent | on HN ]