@SgtPooki thoughts? looks likecustomizing gateway via Settings Screen input loses port info?

it does look like port is being dropped @lidel I can look into this

definitely dropping the port, error is here:

A few things:

1. We are currently checking that both a subdomain url will work, so IP:port from OP won't work, that's an invalid URL. see

   ipfs-webui/src/bundles/gateway.js

   Line 144 in 878975a

   return await checkViaImgUrl(imgSubdomainUrl)

2. We also check that path URLs redirect to subdomains see

   ipfs-webui/src/bundles/gateway.js

   Line 145 in 878975a

   .then(async () => expectSubdomainRedirect(imgRedirectedPathUrl))

potential fixes here:

• display an error to users if they enter an ip address with port, it is invalid
• don't check for subdomains (wouldn't this invalidate the whole change of fix(files): prefer subdomain gw in copied share links #2255)
• display more information in the description for this input that ip:port URLs will not work, and that the URL must support the format {protocol}://{cid}.ipfs.{host}

Thank you for looking into this.

@waseemjaved755 seem to be using older version which had a single setting. since then we've split it into two.

I think we should:

1. add input validation and refuse setting IP-based URL as Subdomain gateway.
2. make sure IP-only URLs are allowed for Path gateway, but also make sure that port is respected