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

Access files by path instead of query #571

Merged
merged 1 commit into from
Aug 6, 2019

Conversation

psiinon
Copy link
Member

@psiinon psiinon commented Aug 2, 2019

I've not updated the changelog as this is an 'internal' change to support #459
URLs used by the HUD to request files and images will now have formats like:

  • https://zap//zapCallBackUrl/<random number>/file/panel.html
  • https://zap//zapCallBackUrl/<random number>/image/target-grey.png

Signed-off-by: Simon Bennetts psiinon@gmail.com

Signed-off-by: Simon Bennetts <psiinon@gmail.com>
Copy link
Contributor

@jaywon jaywon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YES!! This is awesome, thank you so much for doing that. Best I can foresee, this should solve the requirements for refactoring the frontend via referenced PR. 🙇 🎉

Made one small comment, not sure if it's a blocker or not, but approving anyhow as I'd love to get this into develop functionally and re-evaluate how to get the PR merged in.

// Currently only javascript files are returned
msg.setResponseHeader(
API.getDefaultResponseHeader(
"application/javascript; charset=UTF-8",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this have a little more evaluation on file type for setting the header since we'll be serving CSS and image files as well?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those will be served by HudFileProxy which does that.

@thc202 thc202 merged commit 39111d7 into zaproxy:develop Aug 6, 2019
@dscrobonia
Copy link
Contributor

So exciting!!!

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

Successfully merging this pull request may close these issues.

4 participants