Check List

• I have read the CONTRIBUTING guidelines and my PR follows them, also I agree to the MIT license.
• I have read the CODE_OF_CONDUCT and the Developer Certificate of Origin and I agree to follow them.

Check List

• I have read the CONTRIBUTING guidelines and my PR follows them, also I agree to
  the MIT license.
• I have read the CODE_OF_CONDUCT and the Developer Certificate of Origin and I
  agree to follow them.

Description

The configs and setups in the README are good but you can't seperate the path and actual command in the code boxes.

Expected Behavior

Add a $ before the actual commands.

Check List

• I have read the CONTRIBUTING guidelines and my PR follows them, also I agree to the MIT license.
• I have read the CODE_OF_CONDUCT and the Developer Certificate of Origin and I agree to follow them.

Description

Add a CONFIGURATION.md to the docs/ folder to document a detailed configuration guide for the application. Make sure to link it on the README.

Check List

• I have read the CONTRIBUTING guidelines and my PR follows them, also I agree to the MIT license.
• I have read the CODE_OF_CONDUCT and the Developer Certificate of Origin and I agree to follow them.

Description

When testing the url's with a proxy, and the proxy redirects to it's proxy error page, I want to be able to read out some configured information out of that html page, and write it to the report. For example the current_user_group, current_category, etc.

Steps to Reproduce

Request a url which is blacklisted by your proxy and you will probably get a 403.

Expected Behavior

Incase the proxy notices an invalid or unallowed url and redirects to it's reporting/feedback page, I want to grab some information about that page, like f.x category, etc, using the DOM api. The most common case is, the requested url returning the proxies policy response through that requested url.

Actual Behavior

None

Additional Info

Make sure to read the response of the requested but forbidden url. Will normally contain some static html code!

Check List

• I have read the CONTRIBUTING guidelines and my PR follows them, also I agree to
  the MIT license.
• I have read the CODE_OF_CONDUCT and the Developer Certificate of Origin and I
  agree to follow them.

Description

When running the built binary of the program, it can't find the links.json because it's ran from a different path then the project root, also it can't export the report.json.

Steps to Reproduce

Build executable binary from your local project, try to execute from terminal or GUI.

Expected Behavior

Should work as intended when running with go run cmd/main.go

Actual Behavior

Throws error and fails reading/exporting files

Additional Info

Check List

• I have read the CONTRIBUTING guidelines and my PR follows them, also I agree to the MIT license.
• I have read the CODE_OF_CONDUCT and the Developer Certificate of Origin and I agree to follow them.

Description

The issue template's check lists looks pretty ugly, since there are some wrong breaks on the template in .github/ISSUE_TEMPLATE.md

Check List

• I have read the CONTRIBUTING guidelines and my PR follows them, also I agree to the MIT license.
• I have read the CODE_OF_CONDUCT and the Developer Certificate of Origin and I agree to follow them.

Description

Add a deplyoment.md to the docs/ folder, explaining the deployment workflow.

Additional Info

Also make sure to remove the .gitkeep file in the docs/ folder.