Stripping standard ports (80 and 443) from output about gau HOT 5 CLOSED

Hey @michael1026,

I think this could be a good option to add, but not something the tool should do by default. For example, if there is an archived URL for port :8080 and :443, they could be running entirely different services, so it may be beneficial at times to have them.

Furthermore, if we strip the ports, would we default to https:// or http://?

from gau.

if there is an archived URL for port :8080 and :443, they could be running entirely different services

Completely agreed, that's why I wanted to only strip :80 and :443 from the output. Ports like :4443, :8080, :8081, etc would be left alone

Furthermore, if we strip the ports, would we default to https:// or http://?

Correct me if I'm wrong, as I didn't build this tool, but don't the URLs come from the APIs with protocols as is? I don't suggest modifying the protocols at all.

Here's a simple before and after of my suggestion.

Before:

https://example.com/
https://example.com:443/
https://example.com/users
http://example.com:80/forum
http://example.com:8080/dashbaord
http://example.com/user/jim

After:

https://example.com/
https://example.com/
https://example.com/users
http://example.com/forum
http://example.com:8080/dashbaord
http://example.com/user/jim

from gau.

Hey @michael1026,

Sorry, I get what you're saying now. I'm curious what the use-case is for this? All I can think of is for better sorting (sort -u)?

Thanks

from gau.

For the most part, yes. Or with uniq or TomNomNom's anew. I just don't see the need for port 80 and 443 to be specified when they're not necessary. If it's out of scope of this project, I can just write a simple tool that does this for my needs and that's no problem.

from gau.

Hey @michael1026,

Sorry - I forgot about this issue. I don't think I'll write any functionality to strip those ports on the output because it shouldn't make a difference besides a visual preference.

from gau.