normalizing the response headers causes confusion

[ErikOwen]

katana version: v1.1.0

Current Behavior:

When crawling a site with the -jsonl flag, the response headers are lowercased, and - characters are converted to _. This is misleading, because technically both Some-Header and Some_Header are both valid headers. The normalization of the response header prevents the end user from being able to identify what the actual response header was.

But lowercasing the response header makes sense, because the headers are case-insensitive.

Expected Behavior:

Response headers in Kebab-Case are preserved, so Content-Type is reflected as content-type in the JSON output.

Steps To Reproduce:

Run this command:

katana -u https://projectdiscovery.io -d 1 --jsonl --crawl-scope https://projectdiscovery.io --omit-raw --omit-body

See that the report_to HTTP header doesn't match the actual response header from the server (report-to).

Anything else:

Offending code: https://github.com/projectdiscovery/katana/blob/main/pkg/navigation/response.go#L23