-
Notifications
You must be signed in to change notification settings - Fork 3k
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
URL names in dashboard are not HTML escaped #374
Comments
Closing due to lack of activity. Let me know if this is still an issue. |
I just tested this. It's still an issue, and I think we should fix it. |
Can I take it? |
@peterdemin By all means! |
Alright, where do I start? I'm experienced with Python, but new to Locust. |
Uhm, if you've never used locust then you would need to start using it first, enough that you can at least reproduce the error. I'm not even sure where the fix should be applied. Maybe in request_stats() in web.py, on line 111. |
I'm using locust here and there for a few years already :-) Thanks for the guidance. |
Cool, I was confused and thought maybe the hacktoberfest tag had attracted some kind of "drive by contributors" who didnt know what Locust was even for :P |
No, I just felt the urge to contribute back to the project I enjoy and used the Hacktoberfest label to filter low-hanging fruits. |
URL names (for stats) were not HTML-escaped in the dashboard. This made names with angle brackets disappear. For example: ``` self.client.get(url, name='/some-resource/upload/<uuid>') ``` would show up as `/some-resource/upload/` instead of `/some-resource/upload/<uuid>` which is confusing. I added new key to /stats/request - "safe_name" - so that escaping is on the server side and javascript has less logic.
Fixed in #1119 |
Escape HTML entities in endpoint names #374
This can be closed, I believe. |
Thx! |
URL names (for stats) are not HTML-escaped in the dashboard. This makes names with angle brackets disappear. For example:
would show up as
/some-resource/upload/
instead of/some-resource/upload/<uuid>
which is confusing. There could be some XSS security concerns here as well.The text was updated successfully, but these errors were encountered: