question marks are used instead of Russian characters in the request

[djtemasuper]

hello, why when I use Russian characters anywhere in the script, instead of them Turbo Intruder puts question marks everywhere, moreover, when I try to encode a string with Russian characters through str.encode('utf-8'), this function does not convert the string in the Turbo Intruder script although everything works correctly in the python interpreter.

[albinowax]

Turbo Intruder uses Jython which is based on Python 2.7 which stores strings as ASCII. You're using Python 3 locally which handles strings completely differently.

[albinowax]

I'm leaving this open because it's definitely possible there's still Turbo Intruder bugs in this area. If you aren't able to fix your issue it would be useful to have a script that demonstrates the exact problem you're experiencing - eg trying to send a request containing russian characters, or viewing a response with them.

[djtemasuper]

I am experiencing the same problems with non ascii character encoding, different engines have different problems:

1. HTTP2 Engine problem with encoding in the response, instead of the response in the body of the request an incomprehensible set of characters is displayed.
   Request:

POST /post HTTP/2
Host: httpbingo.org
Content-Length: 10
Accept: application/json
Content-Type: text/html; charset=utf-8;
Accept-Encoding: gzip, deflate, br
Accept-Language: ru-RU,ru;q=0.9,en-US;q=0.8,en;q=0.7

пы

Response:

2. BURP2 Engine due to a problem with the encoding of the request body, the server does not respond to the request (errors 400 Bad request, and as in the example, the response in general did not come).
   Request:

POST /post HTTP/2
Host: httpbingo.org
Content-Length: 10
Accept: application/json
Content-Type: text/html; charset=utf-8;
Accept-Encoding: gzip, deflate, br
Accept-Language: ru-RU,ru;q=0.9,en-US;q=0.8,en;q=0.7

пы

Response:

[albinowax]

@djtemasuper with the HTTP2 engine, that looks like brotli encoding. Try removing the 'accept-encoding' request header.

[djtemasuper]

@djtemasuper with the HTTP2 engine, that looks like brotli encoding. Try removing the 'accept-encoding' request header.

Yes, indeed, in the HTTP2 engine the problem was in the Accept-Encoding header, without it the response comes in normally