Skip to content

--exclude-sizes and --min-response-size/--max-response-size measurement units do not match #1489

@shelld3v

Description

@shelld3v

Description

To use --min-response-size/--max-response-size, you have to feed in a value in byte, no suffix, but --exclude-sizes requires you specify a measurement unit by a suffix and it can be byte, kilobyte, ... This makes a big confusion, some people might think you can use --min-response-size/--max-response-size with any unit, using a suffix, some think --exclude-sizes only allows byte value, and you only give it a number. And remember, our output only gives users knowledge about response size in the most compacted unit.

Solution

All 3 should have only 1 way to use, or all 3 should allow both ways to be used. If we support value by bytes, can we somehow let the user knows the response size in bytes through the output?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions