Brion,
Thanks. This is a start.
Unfortunately, as my domain is managed by a different company than my
host (which is the cause of these problems) I can't implement your
easier alternative solution.
However, I now have some more specific questions based on your last
post:
On Aug 4, 2004, at 2:29 PM, Brion Vibber wrote:
Data that's submitted as a POST form can't
make it through from the
parent frame to the child frame, as HTML doesn't allow anything like
that.
But don't these other programs use POST to send data? For instance, in
pagetool I found this command:
echo "<form action=\"" . $admp .
"&pt_action=update&pt_section=www&id=" .
$row["www_id"] .
"\" enctype=\"multipart/form-data\"
method=\"post\">\n";
I'm trying to understand why this works with the EasyDNS URL
forwarding, and POST in MediaWiki does not. Here is the relevant code
from Editpage.php in MediaWiki:
<form id=\"editform\" name=\"editform\" method=\"post\"
action=\"$action\" enctype=\"application/x-www-form-urlencoded\">
This means that the <form> needs to have an
action URL which specifies
the *real* page, not the forwarded (false) page. Since you're
insisting on using the forwarded (false) URLs everywhere, that means
you have to hack all the forms that do POSTs to be an explicit
exception.
I was looking at some of the POST tags in the code, and it seems that
many of them rely upon code in Title.php for their URLs. That file has
a bunch of functions, such as "getFullURL", "escapeLocalURL",
"getEditURL" etc. which seem to be called upon in some of the POST
commands. Might it not be possible to edit some of these functions?
They seem to call upon $wgserver, but setting that didn't have any
affect for me either way.
Cheers,
kkerim