php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #24755 Design-Problem in ISAPI Modul
Submitted: 2003-07-22 13:05 UTC Modified: 2003-07-24 09:43 UTC
From: T dot Hauck at janaserver dot de Assigned:
Status: Wont fix Package: IIS related
PHP Version: 4.3.2 OS: W2K
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: T dot Hauck at janaserver dot de
New email:
PHP Version: OS:

 

 [2003-07-22 13:05 UTC] T dot Hauck at janaserver dot de 
Description:
------------
In the ISAPI-Modul of PHP4 (php4isapi.dll) is a ISAPI-FILTER and an ISAPI-EXTENSION includet. If a authtication is made via Http the username and the password for that authetification is captured by the isapi-filter, when the SF_NOTIFY_AUTHETIFICATION is called. After that the ISAPI-Extension is called to run the script. As long as everything runs from the same thread within the webserver, the username and the password work in the ISAPI-Extension (for example in PhpMyAdmin). But if the ISAPI-Filter is called from a other thread than the ISAPI-Extension within the webserver, the username and password are not avalible. Befor i forget it, this only happends if "register_globals" is OFF! With "register_globals" = ON everything works.

I think it should be interpendend from what thread the filter and the extension is called. I think the server-context of the isapi calles should be the reference, and not the thread-id.

The webserver i use is called JanaServer (www.janaserver.de) in a developer state, what can't be downloaded right now. If someone needs that Serverprogramm, feel free to contact me at T.Hauck@janaserver.de

Sorry for my english, but i'am from Germany.

Regards Thomas Hauck

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-07-24 08:56 UTC] sniper@php.net 
Feel free to provide a patch to fix this?
Does it happen with IIS? How to reproduce?
 [2003-07-24 09:25 UTC] T dot Hauck at janaserver dot de 
>Feel free to provide a patch to fix this?
Soory, but i'am bussy with my own project.

>Does it happen with IIS? 
I don't know, i'am not useing IIS.

>How to reproduce?
You need my webserverprogram, if you like i can send it to you.

Like i wrote in my first email, it is not really a bug. If a webserver switches threads will working on a request, it will not work. I don't know if other webservers are switching thread on a request, but my server design does it. And i think, it should not matter for the php isapi modul if that happens. Other isapi moduls don't have a problem with that.
What i also don't understand, in the ISAPI Extension the "Auth_User" und "Auth_Password" Servervariables are called again, why are they not Working /  be used ?

I alos patched my serverprogram right now, so that the AUTHETIFICATION notification is called a second time from the same thread where the isapi extension is called. That is not nice, but it works.

Regards Thomas
 [2003-07-24 09:43 UTC] wez@php.net 
PHP has strong thread affinity; the thread that starts a request must be the same thread that executes the whole of the request.  This will not ever change.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Apr 20 08:01:30 2024 UTC