On Aug 4, 2004, at 2:50 AM, Brion Vibber wrote: Every other software I've installed on my system: Pagetool TikiWiki ActivePHPBookmarks Nucleus MovableType WordPress Have ALL been able to handle this "crappy forwarding scheme" just fine. Media Wiki is the only one that hasn't. The forwarding system is actually quite robust, it is simply a frame, nothing else. It can handle metatags. The reason I use it is too complex to explain, but many people use such systems, whether because they share hosting with other people, use subdomains, wish to remain able to easily change hosts, etc. That is why all the above software have provisions to allow people to do just that. But all I'm asking is for some help understanding WHY it isn't working. You've been very helpful so far, but obviously you don't wish to help any more. That's fine. But maybe someone else might know why the forms aren't working. Absolute URLs, with the proper domain will all work as if they were on the host domain. I like MediaWiki, and you have all been very helpful up to now. But now I seem to be getting a Micro$oft type of reply: if the software doesn't work the way you want, change how you do things. That isn't why I use open source software! I'm not much of a programmer, so if hacking the forms is truly too complicated, I may just have to give up. But I'd like to give it a try. Thanks again! kerim

I'm not going to get into a tit for tat. If you've read this thread you will see that I've both offered lots of help to newbies (other than just telling them to read the wiki), and I've thanked people for the help I received. I also solved some problems that other people offered partial solutions to, and I explained why the full solution worked better than the partial solution. I was just asking for someone to point me the direction as to where to get started: i.e. where to look in the code. Instead, I was told that I was in the wrong for asking such a question. This is not the kind of attitude I came to this forum with, and it is isn't the kind of attitude I expect from others. Go ahead and defend your friends, but don't do so out of context. kerim On Aug 4, 2004, at 9:18 AM, Shimmie wrote:

P. Kerim friedman wrote: Right, that's what I'm trying to explain. 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. 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. It would be a lot easier for you if you didn't need to pull this frame trick (which will be very inconvenient for visitors using text-based browsers, screen readers, and others in which it introduces an extra navigational barrier on every single page). If you contact your hosting provider, I'm sure they will be happy to set up the alternate domain as an alias if it's necessary (ie, if they're using name-based virtual servers). -- brion vibber (brion @ pobox.com)

On Wed, 4 Aug 2004, P. Kerim friedman wrote: They don't have to be the same, as they are separate services. DNS controls the mapping of hostnames ('foobar.com') to IP addresses ('12.34.56.78'). Hosting puts an actual computer at the network IP address ('12.34.56.78') which responds to external requests, such as HTTP requests for web pages. If multiple sites are served from a single network address ('12.34.56.78'), it is necessary also for the host to be aware which hostnames ('foobar.com', 'superfoo.net') are in use so requests are directed to the right configuration. It is not necessary for the host to control the mapping of hostnames ('foobar.com') to IP addresses ('12.34.56.78'), only to be aware of them, and then only for that particular configuration case (name-based virtual servers sharing an IP address). I apologize if the above sounds patronizing or condescending; I'm really just trying to make things clear. Could you take a look at the actual produced HTML to see what the listed URL is? Is it a full URL including the real hostname, a full URL including the false forwarded hostname or a relative URL? If it's a relative URL and there is no <base href> or it's a full URL with the real hostname, then it's expected that it will work -- it will go directly to the real script without disturbing the frameset. If it's a full URL with the false hostname or a relative url with a <base href> for the false hostname then I would be surprised if it works. The relative hostname is altered by the browser using the <base href> to the false forwarded hostname, thus the post fails. Yes, as I mentioned earlier you can go through and change these functions and it might work. However I expect you'll have a hard time getting the consistent results you seem to want with a frame-forwarding system. -- brion vibber (brion @ pobox.com)