Ville Skyttä

Thanks!

`filter_headers` applies to request headers, so only `Cookie` can be taken care of with it. `Set-Cookie` on the other hand is a response header, and thus needs to be done...

Here's a more elaborate implementation I've been using that does the actual `response["url"]` query param filtering: https://github.com/scop/pytekukko/blob/c43533c8c8ff46f5fc1114e0d19a9cde58c89ae9/tests/test_pytekukko.py#L36-L50 (Nowhere near perfect: it expects replacements, does not do removal, and does not...

Yeah, @rpdelaney's comment is a variant of the problem, although slightly unrelated in the sense that the advice given by this check is quite likely the best possible fix for...

Sure, but the warning needs to be valid in some scenarios on its own. If this lead you to avoid using asserts to signal failure, that I think was a...

In `validate` mode, I would like to validate in the strictest possible sense according to the relevant spec -- the point of validation being ensuring validity and thus likely broadest...

As mentioned, I think the HTTP status code should be a part of the exception thrown there, so users can use that in their decision making. Possibly also some other...

Based on the stack trace it seems to me that this might be a bug in the Bouncy Castle provider. At the point where the problem occurs, Portecle just asks...

Hello, Portecle version is 1.7 Bouncy Castle provider specification version is 1.1 and implementation version is 1.45.0 Best regards Original comment by: galletto

I suggest trying with Bouncy Castle versions 1.43, 1.44, and 1.46 to see if it makes a difference - replace the bcprov.jar that comes with Portecle with each of these...