Last modified: 2011-07-18 05:35:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T12248, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 10248 - Bad link to edit a new page when connecting on a non-standard port
Bad link to edit a new page when connecting on a non-standard port
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.10.x
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://quebec.boucher-frappier.net:88...
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2007-06-13 19:15 UTC by Claude Boucher
Modified: 2011-07-18 05:35 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Claude Boucher 2007-06-13 19:15:07 UTC 
The link to edit a new page in <div class="noarticletext"> points to an external url containing a full URL (http://www.example.com/wiki/index.php?Title=Test&amp;Action=edit) instead of a local URL, relative to the root of the server (/wiki/index.php?Title=Test&amp;Action=edit), which is the case for the "Edit this page" tab. 

When an external user tries to create a new page clicking on the link in <div class="noarticletext"> while using a non-default port (such as port 8889), he/she gets a timeout when the default port 80 is blocked for some reason, such as uptstream ISP restrictions on port 80, which is beyond the control of the server administrator. However, the external user can use the "Edit this page" Tab to create the new page, because this tab uses an URL relative to the root of the server. 

A solution to this problem could be to use a URL relative to the root of the server in <div class="noarticletext"> instead of using a full URL.
Comment 1 Brion Vibber 2007-06-13 19:19:50 UTC 
Ensure that $wgServer is set correctly. Normally this is autodetected.
Comment 2 Dan Collins 2011-07-18 05:35:20 UTC 
Works for me with $wgServer set on 1.19 svn
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links