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.

Sign up for GitHub

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

Jump to bottom

Response header names specified via respond function should be lower cased #1704

Closed
miherlosev opened this issue Jul 31, 2018 · 1 comment
Closed

Response header names specified via respond function should be lower cased #1704

miherlosev opened this issue Jul 31, 2018 · 1 comment
Assignees
@miherlosev
Labels
STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug

Comments

@miherlosev
Copy link
Contributor

miherlosev commented Jul 31, 2018 •
edited
Loading

see DevExpress/testcafe#2681
@miherlosev miherlosev added this to the Sprint #15 milestone Jul 31, 2018
@miherlosev miherlosev self-assigned this Jul 31, 2018
miherlosev pushed a commit to miherlosev/testcafe-hammerhead that referenced this issue Jul 31, 2018
fix 'Response header names specified via respond function should be l…
c269be7 
…ower cased' (close DevExpress#1704)
@miherlosev miherlosev mentioned this issue Aug 14, 2018
Closed
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
@miherlosev @AndreyBelym
fix Response header names specified via respond function should be lo…
8ddaa6d 
…wer cased (close DevExpress#1704) (DevExpress#1705)

* 4

* fix tests

* fix 'Response header names specified via respond function should be lower cased' (close DevExpress#1704)
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@miherlosev miherlosev

Labels
STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@miherlosev