Hi JR,
Okay, so long as you understand the folder logic, let’s get on with your problem.
Is the link a file or a directory? “They’re not the same and won’t display the same on both.”
Sorry, I couldn’t resist! 
Let’s go through your code:
DirectorySlash Off # This caused some troubles (mod_dir was on)
[indent]Thanks for the pointer on this module!
[quote="apache.org"]
The DirectorySlash directive determines, whether mod_dir should fixup URLs pointing to a directory or not.
Typically if a user requests a resource without a trailing slash, which points to a directory, mod_dir redirects him to the same resource, but with trailing slash for some good reasons:
* The user is finally requesting the canonical URL of the resource
* mod_autoindex works correctly. Since it doesn't emit the path in the link, it would point to the wrong path.
* DirectoryIndex will be evaluated only for directories requested with trailing slash.
* Relative URL references inside html pages will work correctly.
Well, if you don't want this effect and the reasons above don't apply to you, you can turn off the redirect with:
# see security warning below!
<Location /some/path>
DirectorySlash Off
SetHandler some-handler
</Location>
[B][COLOR="Red"]Security Warning[/COLOR][/B]
Turning off the trailing slash redirect may result in an information disclosure. Consider a situation where mod_autoindex is active (Options +Indexes) and DirectoryIndex is set to a valid resource (say, index.html) and there's no other special handler defined for that URL. In this case a request with a trailing slash would show the index.html file. But a request without trailing slash would list the directory contents.
[/quote]
:blush: Nice to have Apache verify (and amplify) my warning![/indent]
RewriteEngine On
RewriteBase /beta/ # I did this since its in a sub-directory, i guess i dont need this, embarassing!
DON’T be embarassed! Even the folks at WordPress use this BECAUSE they need to protect against any Redirect statements they can’t be aware of!
# REDIRECTS EVERYTHING to index.php - including index.php
# the result will be index.php?url=index.php
# If you've ever wondered why I "go off" about (.*), this is it!
RewriteRule ^(.*)$ index.php?url=$1 [QSA,L]
# Adding a / to the query string is, well, ridiculous!
RewriteRule ^(.*)$ index.php?url=$1/ [QSA,L] # Practically same thing, tried forcing the slash on alternatively
Okay, knowing that it’s a “social” website that’s driving this helps but I fear that I need to see an example of the URI that you’re trying to use - as part of the need for “Specificity.”
# I know this is wrong, but can't fix it
RewriteCond %{HTTP_HOST} !^\\.swfup\\.com/beta$ [NC]
# a directory is NEVER part of the {HTTP_HOST} variable => false
RewriteRule ^(.+)/$ http://%{HTTP_HOST}/$1 [R=301,L]
# will NEVER be redirected because of the directory in the RewriteCond
RewriteRule ^(.*)$ index.php?url=$1/ [QSA,L]
# same LOOPY problem as above except that it adds a trailing / to the QUERY STRING!
Book? If you are looking for SysAdmin info, Dan Bowen’s The Definitive Guide to Apache mod_rewrite is excellent - and it’s been updated for Apache 2. If you understand the differences between putting your mod_rewrite code in server or VirtualHost configuration files and .htaccess, you’ll do well with this one.
Specificity, if you please. At least, please give us an example of the link you’re attempting to deal with!
Regards,
DK