overide --enable-trans-sid?

[Anonymous]

My webhost has compiled a new php-installation and use the "--enable-trans-sid" parameter during compiletime.

I got a function to make links in my site and to other subdomains in wich the session is kept (for all subdomains). So I don't need that option.

Any way that I can disable it?

Greetz Daan

 

[Anonymous]

Is there any reason why I should make relative links absolute links on my site?

A link on http://www.doppy.nl:
relative: "?dp=1"
absolute: "http://www.doppy.nl/?dp=1"

both will work and result in the same thing, but is there a reason why I should keep the link relative? This ofcourse in combination with the problem described in my first post.

Greetz Daan

 

[Anonymous]

Well, I'm sure I read somewhere that when you're using sessions, PHP automatically appends the session ID to any URLs within your page (before or after generation, cos it looks for them afterwards and appends them before outputting the result after compiling it).

However, I'm sure I tested it recently and it appended the URL on hard links (within the same site) so I'm not sure anymore. Maybe it detected it was within the same site by looking at the current page location.

I honestly don't know, but I use relative when I can because I move my site around too much for it to be hard linked!

 

[Anonymous]

When using absolute links (with domain), the session id is not added to the url.

So I switched to all absolute links, not a problem for me, as all links are created by a function (not hard coded in pages).
The current host is added automaticly by the function if no other host has been supplied, in other words, I'm doing stuff that the browser should be handling :mrgreen:

Greetz Daan

 

[Anonymous]

Oh yeah, well my site's links are created by a function as well! Except the function produces relative links because it checks where it is, and where the destination file is, and then forms the appropriate link by traversing through the directories.

So nah nah nah poo poo

 

[Anonymous]

Mine is easy-er because I've got only one file on my webserver (index.php)
ALL pages are generated form that and some code is fetched from the database and everything is dynamic and can be changed from on the site itself (you need a password for that ofcourse). :wink:

You top that! :wink: :wink:

nahnahnahnahnahnah

:mrgreen: :twisted:

Greetz Daan

"/me wonders when this post will be closed" :mrgreen:

 

[Anonymous]

Mine is easy-er because I've got only one file on my webserver (index.php)
ALL pages are generated form that and some code is fetched from the database and everything is dynamic and can be changed from on the site itself (you need a password for that ofcourse). :wink:

You top that! :wink: :wink:

nahnahnahnahnahnah

:mrgreen: :twisted:

Greetz Daan

"/me wonders when this post will be closed" :mrgreen:

So you tell me Mr Smartypants, if you've just got your index.php file, and someone requests http://www.yoursite.com/this/dir/something/page.php, how does that fetch your index page which would be at http://www.yoursite.com/index.php?

And believe me, my site is fully dymanic. I've got quite a few different functions and classes in use. Problem is all that code makes the page bloated, so I keep them all in a central reservoir, and when the script needs a function it can't find, it'll pull it out of the reservoir so it's faster?

 

[Anonymous]

So you tell me Mr Smartypants, if you've just got your index.php file, and someone requests http://www.yoursite.com/this/dir/something/page.php, how does that fetch your index page which would be at http://www.yoursite.com/index.php?

There is no php/html file located in any subfolder (except for a phpbb, but that one runs stand alone from my code).
When someone requests a file at that location, he will get an error page wich say's that the page is not available and redirects the user to the index.php that is available wich in turn will display a portal-page .
No need for code that will find the index.php, let apache handle that

And believe me, my site is fully dymanic. I've got quite a few different functions and classes in use. Problem is all that code makes the page bloated, so I keep them all in a central reservoir, and when the script needs a function it can't find, it'll pull it out of the reservoir so it's faster?

I believe you
I've also got quite some functions and pieces of code and most of them are fetched from the database and are only "loaded" when needed.
I fetch them from the database (and store some in session-data) because I find include's terribly slow :S:S

Anyway, it seems were both using some fancy code

Greetz MrSmartypants
(A.K.A. Daan)

 

[Anonymous]

You've just got the one page??? That's not very good, what happens when you want to expand the site?

I've also got quite some functions and pieces of code and most of them are fetched from the database and are only "loaded" when needed.
I fetch them from the database (and store some in session-data) because I find include's terribly slow :S:S

Anyway, it seems were both using some fancy code

Greetz MrSmartypants
(A.K.A. Daan)

Not quite. You've obviously got coding in your page to access the database to get the new functions. Which means each page that uses a function has to have the same coding?? Not mine. They've all got about 3 lines each which get them to determine where they are, and where everything else is. Which means ANY page can at ANY time have full access to ANY function it wants. It's taken me 6 months to think of this method of doing things, can't believe I didn't think of it before!