Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

Hotfix: default value for headers is string not null #204

Merged
merged 3 commits into from
Dec 4, 2019
Merged

Hotfix: default value for headers is string not null #204

merged 3 commits into from
Dec 4, 2019

Conversation

michalbundyra
Copy link
Member

As per specification default value for headers should be string, not null.
In many cases it was invalid as we return null instead.

Also, when creating new instance with empty string, again - null was
returned instead.

Fixes #202

As per specification default value for headers should be string, not null.
In many cases it was invalid as we return null instead.

Also, when creating new instance with empty string, again - null was
returned instead.

Fixes #202
Copy link
Member

@froschdesign froschdesign left a comment

Choose a reason for hiding this comment

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

The new unit tests are looking good! 👍

Copy link
Member

@weierophinney weierophinney left a comment

Choose a reason for hiding this comment

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

Looks good. Since HeaderInterface::getFieldValue() specifies a return value of a string, this is definitely a good correction.

🚢

michalbundyra added a commit that referenced this pull request Dec 4, 2019
Hotfix: default value for headers is string not null
michalbundyra added a commit that referenced this pull request Dec 4, 2019
michalbundyra added a commit that referenced this pull request Dec 4, 2019
@michalbundyra michalbundyra merged commit c18aca6 into zendframework:master Dec 4, 2019
@michalbundyra michalbundyra deleted the hotfix/header-field-value branch December 4, 2019 21:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

empty header values in responses are breaking the application since version 2.10.1
3 participants