Opened 11 months ago
Closed 11 months ago
#69013 closed defect (fixed)
MacPorts News Error 503
Reported by: | thomasrussellmurphy (Thomas Russell Murphy) | Owned by: | admin@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | server/hosting | Version: | |
Keywords: | Cc: | ||
Port: |
Description
https://www.macports.org/news/ returns 503 and has for at least a couple days, making the beta release notes for MacPorts base less accessible.
Change History (3)
comment:1 Changed 11 months ago by jmroot (Joshua Root)
Component: | website → server/hosting |
---|---|
Owner: | set to admin@… |
comment:2 Changed 11 months ago by ryandesign (Ryan Carsten Schmidt)
comment:3 Changed 11 months ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Clemens or Rainer, could you check what the Apache log on Braeburn says after you access https://www.macports.org/news/?
As a refresher, all of www.macports.org is served by Apache on our server Braeburn but for URLs under /news it uses a reverse proxy to get its content from GitHub Pages. We configure GitHub Pages in a nonstandard way: we have a CNAME file that tells GitHub to redirect any requests for macports.github.io to www.macports.org so that if some user guesses that our web site might be macports.github.io, they are redirected to the canonical hostname. What's nonstandard about it is that www.macports.org points to Braeburn, not GitHub Pages. The reverse proxy configuration on Braeburn for /news forwards requests to http://macports.github.io/news but sets a custom Host header of www.macports.org so that GitHub Pages will return the real content and not a redirect. On the command line, this is still working for me: