Open globeone opened 3 years ago
Strictly speaking this looks like a local config issue, but no problem with trying to fix invalid or missing paths.
So, there is no check if the Base Directory is blank in the options.
It would be desirable to have a check if the Base Directory field is filled when the 'enable HUD' option is checked to prevent this issue from occurring in the future.
Agreed :)
Describe the bug On the Weekly version of ZAP the HUD hasn't loaded in the browser for the last 4 or so weeks of versions. The HUD is enabled.
To Reproduce Steps to reproduce the behavior:
Expected behavior When launching the HUD, the HUD should show up in the browser
Screenshots
![2020-10-29_OWASP ZAP D-2020-10-26-Firefox_No_HUD_800x604](https://user-images.githubusercontent.com/10052587/97690333-2356a280-1a9d-11eb-9a6d-5252bb9fed4d.jpeg)
Software versions
ZAP: D-2020-10-26
Add-on: D2020-10-26_InstalledPlugins.xlsx
OS: Windows 10
Java: Bellsoft Liberica JDK 15
Browser: Chrome: Version 86.0.4240.111 (Official Build) (64-bit) Firefox: 82.0.2 (64-bit)
Errors from the zap.log file D2020-10-26_ZAPHUD_injectionhtmlNotFound.txt
Additional context In the log file we see that the relative path to injectionHtml.html is incorrect. Java then defaults to a absolute path of No such file C:\target\injectionHtml.html that doesn't exist. the absolute path being (for the weekly version) C:\Users\$USER\OWASP ZAP_D\hud\target\
Would you like to help fix this issue? Happy to test and report bugs.