Custom header input is not working with headless option

[ehsandeep]

Example:

echo example.com | katana -headless -H "GG: test" -j | jq -r .request.raw 

   __        __                
  / /_____ _/ /____ ____  ___ _
 /  '_/ _  / __/ _  / _ \/ _  /
/_/\_\\_,_/\__/\_,_/_//_/\_,_/							 

		projectdiscovery.io

[INF] Current katana version v1.0.1 (latest)
[INF] Started headless crawling for => https://example.com
GET / HTTP/1.1
Host: example.com
User-Agent: Go-http-client/1.1
Accept-Encoding: gzip

Is it not possible to specify the user-agent in headless mode?

$ echo  http://0.0.0.0:65161 | ./katana -headless -H "User-Agent: test" -j

   __        __                
  / /_____ _/ /____ ____  ___ _
 /  '_/ _  / __/ _  / _ \/ _  /
/_/\_\\_,_/\__/\_,_/_//_/\_,_/							 

		projectdiscovery.io

[INF] Current katana version v1.0.1 (latest)
[INF] Started headless crawling for => http://0.0.0.0:65161
{"timestamp":"2023-04-20T17:58:21.140330753+08:00","request":{"method":"GET","endpoint":"http://0.0.0.0:65161","raw":"GET / HTTP/1.1\r\nHost: 0.0.0.0:65161\r\nUser-Agent: Go-http-client/1.1\r\nAccept-Encoding: gzip\r\n\r\n"},"error":"[hybrid:RUNTIME] navigation failed: net::ERR_CONNECTION_REFUSED \u003c- could not navigate target\n"}

In headless mode, the user-agent being used is not the specified one, nor is it similar to what a normal legitimate browser might use.

Originally posted by @heroesm in #270 (reply in thread)