Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Cannot browse to local site with custom port - Firefox removes the port

  • 3 antwoorden
  • 1 heeft dit probleem
  • 76 weergaven
  • Laatste antwoord van onefellswoop

onefellswoop
onefellswoop
more options

For local development on our Macs we use MAMP Pro, which uses the port 8888 for sites.

Since upgrading to Firefox 14, if we enter the URL of a local site into Firefox, it removes the custom port we've added and returns a 403 error. Chrome and Safari work without issue as they don't delete the port.

For example, if I browse to http://my.test.site.localhost:8888 which up until version 14 worked fine, Firefox removes the :8888 and instead tries to load http://my.test.site.localhost, which fails.

If I browse direct to an inner page like http://my.test.site.localhost:8888/page1 it works and the port stays. But it won't work to the root URL.

This is causing major issues for us. It's not a banned port - why is Firefox ignoring the port we enter?

For local development on our Macs we use MAMP Pro, which uses the port 8888 for sites. Since upgrading to Firefox 14, if we enter the URL of a local site into Firefox, it removes the custom port we've added and returns a 403 error. Chrome and Safari work without issue as they don't delete the port. For example, if I browse to http://my.test.site.localhost:8888 which up until version 14 worked fine, Firefox removes the :8888 and instead tries to load http://my.test.site.localhost, which fails. If I browse direct to an inner page like http://my.test.site.localhost:8888/page1 it works and the port stays. But it won't work to the root URL. This is causing major issues for us. It's not a banned port - why is Firefox ignoring the port we enter?

Gekozen oplossing

OK, found it. It was a caching issue. Clearing the cache in FF wasn't fixing it for us. Manually removing everything in the Firefox Cache folder fixed it. Weird.

Dit antwoord in context lezen 👍 0

Alle antwoorden (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Did you try this? http://my.test.site.localhost:8888/

onefellswoop
onefellswoop Vraageigenaar
more options

Yep. Same issue. The port and the trailing slash are removed.

Have cleared caches, dumped cookies, and deleted and fresh installed Firefox. Can't seem to solve it.

onefellswoop
onefellswoop Vraageigenaar
more options

Gekozen oplossing

OK, found it. It was a caching issue. Clearing the cache in FF wasn't fixing it for us. Manually removing everything in the Firefox Cache folder fixed it. Weird.