Skip to content

HTTP 500 after 20 requests, and others? #14

@n00b1990

Description

@n00b1990

First of all thank you very much for providing and updating this project. It comes in very handy :)

I do have the following findings/requests:

  • For some reason http 500 errors are thrown after continuing above 20 requests to the same bin
  • The raw request body is cut off after 10240 characters. A longer body is not caught entirely which makes it difficult to sometimes inspect well. The Content-Length header however does contain the correct length of the content (which is more than 10240)
  • Is it possible to number the requests on the left side (in descending order since the most recent is up top)? This way we can immediately see which request we're dealing with instead of counting from the bottom of the page
  • Maybe a possibility to show it at the top of the page when the bin is "full"? As in that the max amount of requests has been reached for this bin? Maybe a progress bar?
  • More of a question: Is there any impact (e.g. to memory/storage) in changing the max requests to 500 or 1000? And is changing the MAX_REQUESTS variable the only thing that's needed to increase the max requests?

Thanks again!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions