Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'a potentially dangerous' cookie problem #102

Open
MattrCoUk opened this issue Nov 23, 2021 · 0 comments
Open

'a potentially dangerous' cookie problem #102

MattrCoUk opened this issue Nov 23, 2021 · 0 comments

Comments

@MattrCoUk
Copy link

MattrCoUk commented Nov 23, 2021

I'm trying to use browser-sync on Woindows 10 and experiencing a strange issue with cookie security, both in Chrome and FF.

browser-sync adds some of its code, looks like the local BS settings, to one of my website's cookies

<<BS_START>>{"bs":{"hardReload":true,"scroll":{"x":0,"y":0}}}<<BS_START>>

the web browsers go bananas thinking it is HTML and won't reload the page without clearing cookies

I have tried setting-up chrome://flags/ but no luck there,
I've updated the npm, and bs to latest versions npm 8.1.2 and bs 2.27.7
The project I'm working on is a quite large .net web application, I'm trying to use browser-sync in proxy mode. The localhost is set-up with IIS.

launching BS from command line like so
browser-sync --files ....

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant