Dmitry Dygalo

Hi @Lakitna Sorry for being silent for so long :( Thank you for sharing your feedback and a working solution for this issue! Much appreciated :) > This is a...

@Lakitna Thank you so much for providing the details! These cases are definitely something where the UX could be improved :) > I think it would be a great start!...

Sorry for not getting back earlier :) Generally, SaaS will be able to uncover more bugs in a wider range of scenarios and display them much nicer than CLI. Here...

Cool! Thank you for the detailed report! :) I will take a look today

I've skimmed through [RFC 7230](https://tools.ietf.org/html/rfc7230), and it seems like `\x80` is a valid value for an HTTP header. Section [3.2](https://tools.ietf.org/html/rfc7230#section-3.2) defines header field value like this: ``` field-value = *(...

Hmm, interesting. If Schemathesis will have a way to customize this behavior - will it help your use case? To adjust the range for possible characters in HTTP headers. Btw,...

> I would be happy with an option to reduce the char range. At the same time, I think it's worth thinking about future users too. Not having them go...

> When running into an issue like this, can you identify it as an 'Only accepts Latin-1 in headers' situation automatically? If that's possible, you can easily keep the full...

Thanks for providing more context! I'll check this a bit later. Meanwhile, the headers can be filtered with the `filter_headers` hook: ```python import schemathesis @schemathesis.hook def filter_headers(context, headers): for name,...

Thank you for leaving a comment. It is strange, I will look at it over the weekend.