[
https://issues.apache.org/jira/browse/KNOX-2479?focusedWorklogId=521658&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-521658
]
ASF GitHub Bot logged work on KNOX-2479:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Dec/20 12:35
Start Date: 08/Dec/20 12:35
Worklog Time Spent: 10m
Work Description: moresandeep opened a new pull request #391:
URL: https://github.com/apache/knox/pull/391
## What changes were proposed in this pull request?
Fix an issue where set-cookie responses from are broken when backend
services send set-cookies with no spaces.
## How was this patch tested?
Locally tested
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 521658)
Remaining Estimate: 0h
Time Spent: 10m
> set-cookie headers broken when spaces between attributes are missing
> --------------------------------------------------------------------
>
> Key: KNOX-2479
> URL: https://issues.apache.org/jira/browse/KNOX-2479
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Sandeep More
> Assignee: Sandeep More
> Priority: Major
> Fix For: 1.6.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The assumption here is that SET-COOKIE header returned to Knox will always
> have spaces between the fields
> e.g.
> {code:java}
> SESSION=e69d3d08-7452-45cb-90bb-9cdde3fa1342; Path=/; HttpOnly{code}
> Which is not the case when CM returns the SET-COOKIE header
> {code:java}
> SESSION=e69d3d08-7452-45cb-90bb-9cdde3fa1342;Path=/;HttpOnly
> {code}
> Which breaks the Knox logic.
> Examples in RFC [https://tools.ietf.org/html/rfc6265#section-2.2] have
> whitespace but they do not specify format. Since CM uses it and it was
> working up until now Knox should be fixed to support it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
