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

Problems processing large responses #18

Open
roelstorms opened this issue Mar 30, 2017 · 2 comments
Open

Problems processing large responses #18

roelstorms opened this issue Mar 30, 2017 · 2 comments

Comments

@roelstorms
Copy link

I discovered this issue during a pentest where a large js file is downloaded from the server. (length 2885688 bytes). I noticed that the browser kept waiting for a response. When issuing the same request from the repeater, the response was returned successfully. Without the proxy, the js file could also be retrieved via the browser.

Inspecting the issue with Wireshark showed me that the request was issued from Burp to the server and the response was received by my machine and thus by burp. After looking at Burp configs I decided to disable all extensions. This narrowed the problem down to this particular extension. I don't know why the extension inhibits the response from reaching the browser through the proxy. If I have some time I will try to recreate the issue with the error output from Burp.

@pathetiq
Copy link
Owner

Thanks for this, if you can provide the file or a similar one that create the problem I will look it up. JS file are not supposed to be analysed and maybe a bad condition make the extension analyse the file and hang because of the size, etc.

Thanks again for reporting that and I'll wait for more detail.

@roelstorms
Copy link
Author

I had the problem with kendo where they followed "how to do it wrong" from this "tutorial". http://developer.telerik.com/featured/using-ui-libraries-without-the-bloat/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants