All three are valid, let me try to explain the differences:
- The initial post of this thread is meant for getting feedback from users, if it solves all know login issues. So far, I'm satisfied with the results, only Microsoft's Internet Information Server (IIS) still has problems. So something quite similiar to this will probably be used in 1.0.12, I'll discuss some details with Beat in the next days.
- Changing .htaccess will not work on every server, as a special module (mod_rewrite) needs to be loaded by the server. I have no clue how this would look like in IIS, but I doubt it that you can use a .htaccess (written for Apache) on IIS. So this is indeed a good solution, but not really within the scope of Joomla!, as it depends to much on your server config. However, this avoids penalties for duplicate content from search engines, as your content can only be found under one doamin - so it's basically a good thing.
- Changing the configuration.php (or achieving the same thing in any other file) is IMHO out of scope for 1.0.12, as stated earlier by me.
So it's your choice, use what ever solves the issues for you
BTW, thanks to everyone who tested the patch! Let me hear if there is anyone for whom this is not working (except for IIS).
Ok both work for me.... but ... (and I can't not say this)
Basically as a OpenSource development you can't go catering to IIS specific hacks... or you eventually tie yourself in knots...
(or for that matter why not cater to AOL server and Sun, Zeus, roxen etc....)
In theory anyone running IIS is doing so because of a few reasons... it came with XP Pro, they are a corp using only MS products? or that's what thier hoster uses...
All in all IIS is not a very widespread web server anyway... but even less so for the sort of hosting packages that let you run Joomla... so its mainly either home users or corporations ... ?? If a corp is thickheaded enough to run IIS then they will probably run MicroSoft CMS... because running IIS is not something to do for technical reasons but because of policy....
Noone is stopping them running apache... except themselves and the same policy stopping them running apache is likely to stop them running Joomla anyway? Its good Joomla runs on IIS but taking functionality or causing potential problems for its primary platform (apache) just doesn't make sense.
Most individuals with websites either use apache hosting or have some cheap package where you can't install your own stuff anyway... and most individuals running their own servers on their desktop... its just unfortunate IIS is so crap it can't support all functionality in Joomla (or lucky it works at all) ...