Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

encoder stuff

Travis | Last updated: Apr 28, 2015 05:34AM UTC

Url encoding, would be nice if two options exist; one that encodes everything. and one that encodes just the characters that are necessary. I keep seeing apps that are microsoft stacks that seem to dislike characters that are encoded when they dont need to be. I dont think the RFC cares, but apps do :D Within the params tab of a request, it would be nice to have the option for each param to select its encoding/decoding function. So if a param is base64, you can edit it and when you click send the encoding will be seamlessly applied. Goal would be to reduce/eliminate copy and paste between decoder tab and other tabs.

PortSwigger Agent | Last updated: Apr 28, 2015 12:39PM UTC

Thanks for these requests. Regarding encoding of just specific characters, the Decoder tool does not do this but the inline encoding options within the request editor (Context menu / Convert selection) do support it.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.