Timeline for Wordpress redirecting connections on port 8080 to 80
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 25, 2018 at 22:33 | history | tweeted | twitter.com/StackWordPress/status/1000142738191503360 | ||
| May 25, 2018 at 20:36 | answer | added | seebiscuit | timeline score: 2 | |
| Oct 3, 2014 at 2:20 | comment | added | user658182 | @user42826 I've configured apache to use 8080, and, as you described, all links to css, images, and other assets are broken. How do you suggest fixing that wouldn't remove redirects? I've seen a lot of people recommend adding :8080 to the url in settings, but this doesn't feel right. I shouldn't have to configure WP in addition to apache, no? | |
| Feb 21, 2014 at 3:18 | comment | added | Seamus Leahy | Why are you trying to run the site on like this? | |
| Feb 20, 2014 at 19:36 | answer | added | calypso | timeline score: 15 | |
| Feb 20, 2014 at 17:01 | comment | added | user42826 | WP can only be configured to run on one port. It will either be mysite.com or mysite.com:8080 not both. When someone views WP via 8080 (but configured for 80), WP would probably show the page but all links will be 80. | |
| Feb 20, 2014 at 16:07 | review | First posts | |||
| Feb 20, 2014 at 16:08 | |||||
| Feb 20, 2014 at 15:50 | history | asked | calypso | CC BY-SA 3.0 |