Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά παραβίασης».

Μάθετε περισσότερα

Αυτό το νήμα αρχειοθετήθηκε. Κάντε νέα ερώτηση αν χρειάζεστε βοήθεια.

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

  • 3 απαντήσεις
  • 1 έχει αυτό το πρόβλημα
  • 180 προβολές
  • Τελευταία απάντηση από onefellswoop

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?

Επιλεγμένη λύση

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.

Προβολή απάντησης εντός συζήτησης 👍 0

Όλες οι απαντήσεις (3)

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

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.

Επιλεγμένη λύση

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.