Skip to content

Session: nette-browser cookie may be sent with secure flag#102

Closed
PavelJurasek wants to merge 1 commit intonette:masterfrom
PavelJurasek:feature-secure-nette-browser
Closed

Session: nette-browser cookie may be sent with secure flag#102
PavelJurasek wants to merge 1 commit intonette:masterfrom
PavelJurasek:feature-secure-nette-browser

Conversation

@PavelJurasek
Copy link
Contributor

No description provided.

$this->response->setCookie(
'nette-browser', $_SESSION['__NF']['B'],
Response::BROWSER, $cookie['path'], $cookie['domain']
Response::BROWSER, $cookie['path'], $cookie['domain'], $cookie['secure']
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Why not pass httponly option as well?
  • This has been removed in 0aed1a2, not sure why

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, I'll add httponly too.

@PavelJurasek PavelJurasek force-pushed the feature-secure-nette-browser branch from 7c5bda3 to 223aebc Compare September 15, 2016 10:34
@dg
Copy link
Member

dg commented Sep 19, 2016

What's the reason?

@PavelJurasek
Copy link
Contributor Author

Mixed content is being sent when site in on HTTPS.

@dg
Copy link
Member

dg commented Sep 19, 2016

It is error message? In which browser?

@PavelJurasek
Copy link
Contributor Author

PavelJurasek commented Sep 19, 2016

There is no error nor warning in browsers. At least not when HSTS is used.
Mozilla Observatory:
screen

PS: this is not urgent and necessary PR

@dg
Copy link
Member

dg commented Sep 26, 2016

Closed by #103

@dg dg closed this Sep 26, 2016
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

Successfully merging this pull request may close these issues.

3 participants