Why the <A> XHTML tag is not allowed in wikitext? How this decision was taken?
On Jan 14, 2005, at 11:56 PM, NSK wrote:
Why the <A> XHTML tag is not allowed in wikitext? How this decision was taken?
MediaWiki's formatting is derived from UseMod's, which does not include <a> among the (optional) allowed tag subset. UseMod's formatting is derived from the original wiki's, which does not allow any HTML.
There is already a standard wiki syntax for hyperlinking, leaving little purpose to choosing to support an <a> tag in addition. Supporting the <a> tag would additionally require extra code in the HTML sanitization code to strip javascript: URLs to maintain security.
-- brion vibber (brion @ pobox.com)
On Saturday 15 January 2005 10:15, Brion Vibber wrote:
HTML sanitization code to strip javascript: URLs to maintain security.
Support for the A tag in MW would be very beneficial for sites that re-publish HTML-coded articles in wikis. TikiWiki has a per-page option to allow full HTML in individual wiki pages and also an HTML-to-wikitext converter. So, in TikiWiki, you can paste HTML code in the editbox and it will be automatically converted to wikitext.
Hi all,
I've been banging my head against the wall for a week trying to get MediaWiki to work through an SSL reverse proxy. In my case stunnel, but the same should apply to any reverse proxy.
Media Wiki incorrectly determines the IP, port, and protocol when running through a reverse proxy. It assumes that the host address is the internet facing address. When using a reverse proxy this is not the case.
I have documented my solution briefly here:
http://www.baus.net/stunnelmediawikisolved
Christopher Baus
======== Implementing an HTTP proxy? Consider a fast, secure alternative http://www.baus.net/ads/license
On Jan 15, 2005, at 2:44 AM, christopher@baus.net wrote:
Media Wiki incorrectly determines the IP, port, and protocol when running through a reverse proxy. It assumes that the host address is the internet facing address. When using a reverse proxy this is not the case.
If you are not running on the canonical host, set $wgServer explicitly in your configuration. This is well documented in the list archives here, and it's one of the earliest options in DefaultSettings.php where you should see it pretty quickly when you go to look up the options.
I finally found it by looking through the DefaultSettings.php file
which is supposed > to be a black box. So much for the quick and easy setup.
DefaultSettings.php is most assuredly not "supposed to be a black box". It is *the* canonical reference for all options you can set in LocalSettings.php, and is liberally commented for that purpose.
-- brion vibber (brion @ pobox.com)
If you are not running on the canonical host, set $wgServer explicitly in your configuration. This is well documented in the list archives here, and it's one of the earliest options in DefaultSettings.php where you should see it pretty quickly when you go to look up the options.
I wasn't sure what to google for, but I didn't find this right away.
DefaultSettings.php is most assuredly not "supposed to be a black box".
Ok, I take that back. If it isn't supposed to be a black box, a quick mention of it in the INSTALL file would be helpful, although it does say:
"Chances are good there's a crucial step that hasn't made it into the documentation."
Which I guess is acurate.
Here's the comment in DefaultSettings.php:
/** * URL of the server * It will be automaticly build including https mode * @global string $wgServer */
It doesn't mention proxies here. What is frustrating is that install.php worked, and didn't report an error. Certainly the installer doesn't know it is running behind a proxy. I immediately went to LocalSettings.php, but no joy.
I finally figured out that redirect.php was redirecting the wrong URI, then I went looking through the redirect.php code to see how the URI was built, which then took me to the DefaultSettings.php.
I'm willing to modify the INSTALL file to either describe the LocalSettings.php/DefaultSettings.php relationship, or point to a document that does.
Christopher Baus
======== Implementing an HTTP proxy? Consider a fast, secure alternative http://www.baus.net/ads/license
mediawiki-l@lists.wikimedia.org