Non-value attributes in Set-Cookie header #1171
According to RFC 6265, section 5.2 these two cases should have the same outcome: empty value.
I am proposing to change the parser to assign a zero-length string to value-less attributes, which would have the following effect:
I will implement the change in a few weeks unless anybody brings up concerns.
The text was updated successfully, but these errors were encountered:
The change seems correct. I'm just wondering if we can incorporate all the changes you've made to be more rfc complaint into @vinamrabhatia work too.
@vinamrabhatia Have you looked into nnposter's commits related to http and cookies? It would be great for you to consider them in your final revision.