-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
hyper tests are broken since ca15b7512e #10009
Comments
The conversion could then be done explicitly without caring if it looks like HTTP or not. |
Eh, no. Because then we also add CRLF to the body in |
I remember myself walking down that line of thinking. That is why I sticked to the HTTP pattern that was in place for hyper. The trouble we have now is that it also replaces \r\n with \r\r\n, it seems. |
I'm trying out a few things in #10010. I want to be able to mark individual sections as |
Another idea would be to have some sort of |
Or just a |
A challenge is to introduce such a new/better/different system in a way that can be gradually transitioned into, without us having to update 800+ test cases in a single blow. |
I was thinking of gradually changing test cases to use the new section. The old way of setting the server response could be left unchanged. But that is just a thought, you know best. |
If I can get this working with my current simpler approach, I think I'll stick to this for now. |
The `crlf="yes"` attribute and "hyper mode" are now only applied on a subset of dedicated sections: data, datacheck, stdout and protocol. Updated test 2500 accordingly. Also made test1 use crlf="yes" for <protocol>, mostly because it is often used as a template test case. Going forward, using this attribute we should be able to write test cases using linefeeds only and avoid mixed line ending encodings. Fixes #10009
I did this
Build curl with hyper
Problem
I think the new
crlf="yes"
support from commit ca15b75 should only be applied to the section where it is used, and not on the entire test case like it is now. Test 2500 only uses it for<data>
so only that content should get crlf replaced.The text was updated successfully, but these errors were encountered: