We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 24865
    • 289 Posts
    Hey guys,

    After a migrating from a local WAMP (Windows 64bit) installation to a Linux based webserver (online) I noticed that each custom created URL, with the help of the $_REQUEST global, contains at the very least a PHPSESSID and sometimes even the ys-modx- from the manager' ExtJS treelist. Now, MODX thankfuly works around it with the link creation, but I see no reason why $_REQUEST should be filled with $_COOKIE information. Is this just me, is it the server or is this a real bug in MODX?

    Thanks in advance!
      @MarkGHErnst

      Developer at Adwise Internetmarketing, the Netherlands.
      • 22303 MODX Staff
      • 10,725 Posts
      Quote from: ReSpawN at Aug 31, 2011, 03:13 PM
      Hey guys,

      After a migrating from a local WAMP (Windows 64bit) installation to a Linux based webserver (online) I noticed that each custom created URL, with the help of the $_REQUEST global, contains at the very least a PHPSESSID and sometimes even the ys-modx- from the manager' ExtJS treelist. Now, MODX thankfuly works around it with the link creation, but I see no reason why $_REQUEST should be filled with $_COOKIE information. Is this just me, is it the server or is this a real bug in MODX?
      The $_REQUEST global always carries the GPC variables (based on your configuration's GPC loading order; see the php.ini directive called gpc_order). GPC stands for $_GET, $_POST, and $_COOKIE.
        • 24865
        • 289 Posts
        Hmm, this is the first I've seen it. I'm gonna install another MODX this evening and see if it is MODX that does it, or a bad server configuration. In any case, it's damn ugly.

        I'll see if I can change it and report back with any result. wink Thanks Jason.
          @MarkGHErnst

          Developer at Adwise Internetmarketing, the Netherlands.