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

[dev.icinga.com #11126] Invalid cookie value in cookie icingaweb2-tzo #2287

Closed
icinga-migration opened this issue Feb 9, 2016 · 3 comments
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Feb 9, 2016

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11126

Created by henkwiedig on 2016-02-09 16:19:28 +00:00

Assignee: (none)
Status: Resolved (closed on 2016-02-25 12:25:04 +00:00)
Target Version: 2.2.0
Last Update: 2016-02-25 12:25:04 +00:00 (in Redmine)


Icingaweb2 generates an invalid cookie value.
For example:

Cookie: icingaweb2-session=1455034035; Icingaweb2=f5krvchq8398bmfaa5dmctkau4ndu8km; icingaweb2-tzo=3600,0

A comma is not an allowed character according to RFC 6265 Section 4.1.1.

cookie-octet = %x21 / %x23-2B / %x2D-3A / %x3C-5B / %x5D-7E
; US-ASCII characters excluding CTLs,
; whitespace DQUOTE, comma, semicolon,
; and backslash

Changesets

2016-02-25 12:21:34 +00:00 by aklimov af18334

Cookie icingaweb2-tzo: use `-' as separator

fixes #11126
@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Feb 18, 2016

Updated by elippmann on 2016-02-18 11:36:43 +00:00

  • Subject changed from invalid cookie value in cookie icingaweb2-tzo to Invalid cookie value in cookie icingaweb2-tzo
  • Category set to Framework
  • Target Version set to Backlog

Hi,

Thanks for the report. Will be fixed in one of our next releases.

Best,
Eric

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Feb 18, 2016

Updated by tgelf on 2016-02-18 17:38:29 +00:00

  • Target Version changed from Backlog to 2.2.0

I guess we can fix this with one or two lines of code ;)

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Feb 25, 2016

Updated by aklimov on 2016-02-25 12:25:04 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset af18334.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.