Sander van Beek

It could, but I'd prefer it as a separate rule. I think there is value in making rules have the smallest possible scope.

True, but the worst that can happen is getting a double error. Besides, there are definitely people, myself included, who simply disable rules they don't like instead of looking at...

Hmmm `assume` is interesting. I did not know about it yet, seems very useful for my #1142 workaround. However, if I understand its purpose correctly, it would result in non-200...

> Maybe it could be generalized so that the user can supply a custom "wrapping" check. Sounds good. I guess the first step to that would be to have an...

We are getting to a situation where more teams want to start using Schemathesis, but I've seen them go wrong on this a few times now. The situation is generally...

> Could you, please, provide more context on this? Surely I'd like to avoid this kind of behavior from the Schemathesis side. It is actually quite easy to create a...

> P.S. I am currently working on a SaaS platform that will provide more features than Schemathesis with a better UX (I hope!! especially on the reporting side). Let me...

Hmm reading a bit in 3.2: 3.2.4: > Historically, HTTP has allowed field content with text in the ISO-8859-1 charset [ISO-8859-1], supporting other charsets only through use of [RFC2047] encoding....

Yeah that would help for me. One extra thing I noticed though, Postman also does not support all these characters in headers. For example: `0x80` (= `ƒ`) results in this...

> so far I didn't see popular stacks from Python / Rust / Go / JavaScript worlds complaining about that matter It's a first for me too, but now that...