Adods - 23 April 2008 09:06 PM

Yes, but if user call url like: http://www.domain.com/controller/method

will this script return ‘http://www.domain.com’ or ‘http://www.domain.com/controller/method’??

only http://www.domain.com/, but if your application is in a subfolder, then http://www.domain.com/subfolder/

I would just like to say that I use this with CodeExtinguisher and haven’t had problems with myself or anyone using codeextinguisher

I neglected to add the last line in the code, though it could probably be pieced together from the previous posts:

As already said, this would return only the base http://www.domain.com/ or http://www.domain.com/subdirectory/ depending on what you specify for “$server .= ‘subdirectory/’ when testing on localhost.

The main advantage we’ve got now is the handling of http/https, you’ll still need to update your subdirectory for each project’s config.php file…

bhogg - 24 April 2008 12:09 PM

I neglected to add the last line in the code, though it could probably be pieced together from the previous posts:

$proto = "http" .
    ((isset($_SERVER['HTTPS']) && $_SERVER['HTTPS'] == "on") ? "s" : "") . "://";
$server = isset($_SERVER['HTTP_HOST']) ?
    $_SERVER['HTTP_HOST'] : $_SERVER['SERVER_NAME'];
$server .= '/';

    if (strstr($server, 'localhost'))
        $server .= 'subdirectory/';
        
$config['base_url']    = $proto . $server;

As already said, this would return only the base http://www.domain.com/ or http://www.domain.com/subdirectory/ depending on what you specify for “$server .= ‘subdirectory/’ when testing on localhost.

The main advantage we’ve got now is the handling of http/https, you’ll still need to update your subdirectory for each project’s config.php file…

But my original contribution already handles subdirectory, maybe you can just combine the two, where you handle the protocol.

We’ll need to tweak it a bit more… doesn’t basename() return the final portion of the URL?  So with someone accessing a page such as:

http://localhost/subdirectory/controllername/function/parm1/parm2

It would return something like “http://localhost/subdirectory/controllername/function/parm1” with the last piece removed.  We could use a simple search for the first / after the root URL to get the subdirectory, if we limit it to one level deep.  But what about when it’s launched to http://www.domain.com? Wouldn’t it then interpret the controllername as the subdirectory instead?

Brian

bhogg - 24 April 2008 11:50 PM

We’ll need to tweak it a bit more… doesn’t basename() return the final portion of the URL?  So with someone accessing a page such as:

http://localhost/subdirectory/controllername/function/parm1/parm2

It would return something like “http://localhost/subdirectory/controllername/function/parm1” with the last piece removed.  We could use a simple search for the first / after the root URL to get the subdirectory, if we limit it to one level deep.  But what about when it’s launched to http://www.domain.com? Wouldn’t it then interpret the controllername as the subdirectory instead?

Brian

Nope. That’s why we are getting the scriptname, because we are only looking at the location of index.php only, and not actually processing the whole url. Why don’t you try it first so you’ll know.

I’ve tested this approach even if the application is in a sub/sub/subfolder, it wouldn’t matter.

I did try it first and it was cutting off the subdirectory, likely since I’m not using index.php (mod rewrite)…

My apologies, I had an extra $server .= “/”; in there from a previous version of the code, your code works just fine!

Thanks for this. I will probably change servers a few times so this is always handy

This is what I use:

Why do you need to include the domain? If you just use a relative (relative server?) path, you don’t need to worry about the domain or the protocol.