Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DSL extractors to extract response effective size #1565

Closed
j4cqui opened this issue Feb 2, 2022 · 2 comments · Fixed by #1873 or #1885
Closed

DSL extractors to extract response effective size #1565

j4cqui opened this issue Feb 2, 2022 · 2 comments · Fixed by #1873 or #1885
Assignees
Labels
Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@j4cqui
Copy link

j4cqui commented Feb 2, 2022

Please describe your feature request:

Can you add the possibility to see the size of the response.

Web server doesn't always send the Content-Length header, and that can be a great improvement to have the size of the response.

Describe the use case of this feature:

When you are using some templates to dump information, which can be useful to see which one is dumping the largest or not only one information. Or when you are working on large scope to prioritize certain assets.

@j4cqui j4cqui added the Type: Enhancement Most issues will probably ask for additions or changes. label Feb 2, 2022
@ehsandeep ehsandeep added the Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix label Mar 24, 2022
@Mzack9999
Copy link
Member

Mzack9999 commented Apr 4, 2022

The response size (calculated on the effective body length) is already available among the matchers. Hence it's already possible to filter out the assets according to any specific logic. For a quick flyover of the targets, probably httpx would be a better option.
Todo:

  • Ensure length can be used among extractors

@Mzack9999 Mzack9999 added the Status: On Hold Similar to blocked, but is assigned to someone label Apr 4, 2022
@Mzack9999 Mzack9999 self-assigned this Apr 4, 2022
@Mzack9999 Mzack9999 added Status: In Progress This issue is being worked on, and has someone assigned. and removed Status: On Hold Similar to blocked, but is assigned to someone labels Apr 19, 2022
@Mzack9999 Mzack9999 linked a pull request Apr 20, 2022 that will close this issue
4 tasks
@Mzack9999 Mzack9999 removed the Status: In Progress This issue is being worked on, and has someone assigned. label Apr 20, 2022
@Mzack9999 Mzack9999 changed the title Response Size DSL extractors to extract response effective size Apr 20, 2022
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Apr 21, 2022
@ehsandeep ehsandeep linked a pull request Apr 22, 2022 that will close this issue
@ehsandeep
Copy link
Member

@j4cqui now you can do with using newly added DSL extractors:

    extractors:
      - type: dsl
        dsl:
          - "len(body)"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants