Ankündigung

Einklappen
Keine Ankündigung bisher.

Zwei verschiedene Virtual Host haben gleichen Session Inhalt

Einklappen

Neue Werbung 2019

Einklappen
X
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

  • Zwei verschiedene Virtual Host haben gleichen Session Inhalt

    Hallo Leute,

    ich hab Windows Server 2003 mit IIS und will gerade das so machen das man wenn ich website a und website b die auf dem gleichen Server sind hab, dass deren session extra gespeichert wird damit sie sich nicht überkreuzen.

    Könnt ihr mir vielleicht bitte sagen wie ich das in php.ini so einstell?

    Mit freundlichen Grüßen
    b_reath


  • #2
    Sessions sollten sich nicht zwischen unterschiedlichen virtuellen Hosts überschneiden.

    Falls sie es doch tun solltest du zuerst an der Serverkonfiguration arbeiten. Ansonsten kannst du session handler nutzen um die Sessions selbst zu speichern und dich manuell darum zu kümmern, wo was liegt.
    sigpic

    Kommentar


    • #3
      Wo find ich diese Serverkonfiguration den genau?

      Kommentar


      • #4
        RTFM: http://www.php.net/manual/en/session.configuration.php

        Kommentar


        • #5
          [Session]
          ; Handler used to store/retrieve data.
          session.save_handler = files

          ; Argument passed to save_handler. In the case of files, this is the path
          ; where data files are stored. Note: Windows users have to change this
          ; variable in order to use PHP's session functions.
          ; As of PHP 4.0.1, you can define the path as:
          ; session.save_path = "N;\path"
          ; where N is an integer. Instead of storing all the session files in
          ; /path, what this will do is use subdirectories N-levels deep, and
          ; store the session data in those directories. This is useful if you
          ; or your OS have problems with lots of files in one directory, and is
          ; a more efficient layout for servers that handle lots of sessions.
          ; NOTE 1: PHP will not create this directory structure automatically.
          ; You can use the script in the ext/session dir for that purpose.
          ; NOTE 2: See the section on garbage collection below if you choose to
          ; use subdirectories for session storage
          session.save_path = "C:\WINDOWS\Temp"

          ; Whether to use cookies.
          session.use_cookies = 1

          ; This option enables administrators to make their users invulnerable to
          ; attacks which involve passing session ids in URLs; defaults to 0.
          ; session.use_only_cookies = 1

          ; Name of the session (used as cookie name).
          session.name = PHPSESSID

          ; Initialize session on request startup.
          session.auto_start = 1

          ; Lifetime in seconds of cookie or, if 0, until browser is restarted.
          session.cookie_lifetime = 0

          ; The path for which the cookie is valid.
          session.cookie_path = /

          ; The domain for which the cookie is valid.
          session.cookie_domain =

          ; Handler used to serialize data. php is the standard serializer of PHP.
          session.serialize_handler = php

          ; Define the probability that the 'garbage collection' process is started
          ; on every session initialization.
          ; The probability is calculated by using gc_probability/gc_divisor,
          ; e.g. 1/100 means there is a 1% chance that the GC process starts
          ; on each request.

          session.gc_probability = 1
          session.gc_divisor = 100

          ; After this number of seconds, stored data will be seen as 'garbage' and
          ; cleaned up by the garbage collection process.
          session.gc_maxlifetime = 1440

          ; NOTE: If you are using the subdirectory option for storing session files
          ; (see session.save_path above), then garbage collection does *not*
          ; happen automatically. You will need to do your own garbage
          ; collection through a shell script, cron entry, or some other method.
          ; For example, the following script would is the equivalent of
          ; setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
          ; cd /path/to/sessions; find -cmin +24 | xargs rm

          ; PHP 4.2 and less have an undocumented feature/bug that allows you to
          ; to initialize a session variable in the global scope, albeit register_globals
          ; is disabled. PHP 4.3 and later will warn you, if this feature is used.
          ; You can disable the feature and the warning separately. At this time,
          ; the warning is only displayed, if bug_compat_42 is enabled.

          session.bug_compat_42 = 1
          session.bug_compat_warn = 1

          ; Check HTTP Referer to invalidate externally stored URLs containing ids.
          ; HTTP_REFERER has to contain this substring for the session to be
          ; considered as valid.
          session.referer_check =

          ; How many bytes to read from the file.
          session.entropy_length = 0

          ; Specified here to create the session id.
          session.entropy_file =

          ;session.entropy_length = 16

          ;session.entropy_file = /dev/urandom

          ; Set to {nocache,private,public,} to determine HTTP caching aspects
          ; or leave this empty to avoid sending anti-caching headers.
          session.cache_limiter = nocache

          ; Document expires after n minutes.
          session.cache_expire = 180

          ; trans sid support is disabled by default.
          ; Use of trans sid may risk your users security.
          ; Use this option with caution.
          ; - User may send URL contains active session ID
          ; to other person via. email/irc/etc.
          ; - URL that contains active session ID may be stored
          ; in publically accessible computer.
          ; - User may access your site with the same session ID
          ; always using URL stored in browser's history or bookmarks.
          session.use_trans_sid = 0

          ; The URL rewriter will look for URLs in a defined set of HTML tags.
          ; form/fieldset are special; if you include them here, the rewriter will
          ; add a hidden <input> field with the info which is otherwise appended
          ; to URLs. If you want XHTML conformity, remove the form entry.
          ; Note that all valid entries require a "=", even if no value follows.
          url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=,fields et="
          Müsste doch eigentlich alles stimmen.

          Ich hab jetzt was rausgefunden.
          Ich hab alle beide websites per ip:80 und ip:81 aufgerufen... Wenn ich jetzt aber statt ip:80 den generischer Hostname nehme, ist der Wert der Session schon unteschiedlich...

          Kommentar

          Lädt...
          X