Last modified: 2010-05-15 15:37:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6556 - Port number not included in 301 forwards
Port number not included in 301 forwards
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Redirects (Other open bugs)
1.5.x
PC Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-05 20:03 UTC by ioldanach
Modified: 2010-05-15 15:37 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description ioldanach 2006-07-05 20:03:37 UTC
My server is configured to use port 8000.  The url I post looks like
http://example.com:8000/wiki/

Sometime prior to my current version this worked fine, but recently I upgraded
to 1.5.8 (the most recent rpm I see available for my system) and the wiki
stopped working properly.  I discovered that in some cases the port number is
not being attached to the 301.  The url above is one instance, the other
instance is when I submit a page edit the edit is accepted but it tries to
forward me back to the same page with the port number removed, which doesn't work.
Comment 1 Robert Treat 2006-08-19 05:34:44 UTC
FWIW this is fixed in 1.8 SVN.  I run with non-standard port all the time with
no problems. 
Comment 2 Dan Li 2006-08-19 17:58:11 UTC
Same here. I think it works in 1.7.1 as well.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links