| Re: Accessing IIS variables from PHP after URL Rewrite [message #177139 is a reply to message #177132] |
Thu, 23 February 2012 13:54   |
Erwin Moller
Messages: 228
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 2/23/2012 2:29 PM, The Natural Philosopher wrote:
> Erwin Moller wrote:
>> On 2/23/2012 12:26 AM, The Natural Philosopher wrote:
>>> Peter Heald wrote:
>>>> On Feb 17, 3:32 pm, Peter Heald <petehe...@gmail.com> wrote:
>>>> > Hi all,
>>>> >
>>>> > I have a working URL Rewrite rule (that simply steps 'up' one dir on
>>>> > the site) and as part of the rule, I set a server variable. However I
>>>> > cannot access this from PHP. I always get the old value of the
>>>> > variable; it's as if the rule never set the variable (or perhaps PHP
>>>> > is picking it up from a cached $_SERVER array containing the old
>>>> > variables?). I've tried existing variables (such as REQUEST_URI) and
>>>> > new variables. Either way, I add it to the list of allowed variables
>>>> > in IIS. I've tried the rule at site level and dir level, nothing seems
>>>> > to help. As I say, the rule works fine, there are no errors, just the
>>>> > variable value is not set. It's driving me nuts - any help would be
>>>> > much appreciated!
>>>> >
>>>> > Pete
>>>>
>>>> Problem is solved. In fact, many of the problems I've been
>>>> experiencing seem to suddenly be ok after applying a heap of Windows
>>>> Update patches to the server...
>>>
>>> why ever would one run php on a windows server?
>>
>> Because the boss/client says so.
>> Because the IT-professionals maintaining the system can only maintain
>> Microsoft systems.
>> Well, I guess you can think up a few yourself too. :-)
>>
>
> Like the IT manager was brain damaged at birth.
> Or is paid a huge kickback from Gatesy.
>
>
> But none of these would seem to apply to the poster, who displays almost
> normal intelligence.
>
:-)
I understand your irritation.
I have seen a lot Microsoft-only companies, big and small.
Especially the smaller ones can't afford a real IT staff and just do
things the way they do things at home, where, of course, they run some
version of windows. And hence they roll out MS-only solutions at work too.
And the longer they invested in it, the harder it is to change.
(Also psychology and pride plays an important role: "I told my company
to use only Microsoft, so that must have been the right choice.".)
I also met many people with low/none IT skills who associate anything
non-Microsoft with "hackers", "crackers", "geeks", etc, and so they
don't trust it.
In the meantime, most systems that *are* compromised are running
Microsoft software.
I don't know how this kind of double-thinking was implemented on the
public at large, but that's how it is nowadays.
I for myself stopped caring too much, and just use whatever is thrown at
me. ;-)
If I start a new project, and the client asks for my advice I will tell
them to use Postgresql/PHP on some nice distro. :-)
But most often the environment is already set to Microsoft, and I am
happy if I can use PHP, even if it is on Windows.
PHP on IIS7 instead of Apache? Fine too.
Anything beats Classic ASP on IIS. ;-)
Regards,
Erwin Moller
--
"That which can be asserted without evidence, can be dismissed without
evidence."
-- Christopher Hitchens
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]