Bug #45062 [Opn->Wfx]: thttpd problem displaying .html pages when patched with php on 64 bits OS

From: Date: Fri, 01 May 2015 19:55:18 +0000
Subject: Bug #45062 [Opn->Wfx]: thttpd problem displaying .html pages when patched with php on 64 bits OS
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-192447@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=45062&edit=1

 ID:                 45062
 Updated by:         cmb@php.net
 Reported by:        j dot orfeuil at courantmultimedia dot fr
 Summary:            thttpd problem displaying .html pages when patched
                     with php on 64 bits OS
-Status:             Open
+Status:             Wont fix
 Type:               Bug
 Package:            Other web server
 Operating System:   debian 4.0 x86_64
 PHP Version:        5.2.6
-Assigned To:        
+Assigned To:        cmb
 Block user comment: N
 Private report:     N

 New Comment:

The thttpd SAPI will be removed from PHP 7[1], so I assume nobody
will take care to fix this issue (if it hasn't already be fixed in
the meantime).

[1] <https://wiki.php.net/rfc/removal_of_dead_sapis_and_exts#sapithttpd>


Previous Comments:
------------------------------------------------------------------------
[2009-07-21 07:33:35] j dot orfeuil at courantmultimedia dot fr

And i still need to provide a backtrace i guess...
I'll do that as soon as i can but as i said in the previous post i'm not working on it
right now.
Thx)

------------------------------------------------------------------------
[2009-07-21 07:31:44] j dot orfeuil at courantmultimedia dot fr

Yes that's what i thought.
This issue is not anymore an urgent problem for me but i guess it will become one again when we will
be back to the task using it....

Does anyone know someone able to update thttpd patch for php on 64bits?

Thanks for your support)

------------------------------------------------------------------------
[2009-07-20 22:56:42] kalle@php.net

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php
for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php
for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.



------------------------------------------------------------------------
[2008-11-21 16:31:48] jani@php.net

Sascha aka sas@php.net but I don't think he's around anymore.

------------------------------------------------------------------------
[2008-11-21 15:42:26] j dot orfeuil at courantmultimedia dot fr

Ok thx for the answer :)
Is there any way to find out who worked on this sapi? Maybe it could help to contact him directly...

Anyway i'll try to provide a backtrace of what's going on. At least, this will make things
clear and provide a lead for solving :)
Thx for this link :)

thank you guys for your help and see you soon with the backtrace.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=45062


--
Edit this bug report at https://bugs.php.net/bug.php?id=45062&edit=1


Thread (18 messages)

« previous php.bugs (#192447) next »