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

go to bug id or search bugs for

Bug #17249 phpinfo() no longer works under SSL
Submitted: 2002-05-15 09:50 UTC Modified: 2002-07-28 01:00 UTC
Votes:3
Avg. Score:4.7 ± 0.5
Reproduced:2 of 2 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: dave at dsb3 dot com Assigned:
Status: No Feedback Package: Scripting Engine problem
PHP Version: 4.2.1 OS: Solaris 8
Private report: No CVE-ID: None
View Developer Edit
 [2002-05-15 09:50 UTC] dave at dsb3 dot com 
Just installed php 4.2.1 (over previous 4.2.0 installation).  Did not make any changes to the apache conf or php.ini config (my php.ini is identical to php.ini-recommended except for expose_php = Off, though I've confirmed this happens with both Off and On).

If I try to view .php pages under SSL, they all work except for a specific file containing only:

--- begin file ---
  <? phpinfo(); ?>
---  end file  ---

If, however, the phpinfo() call is within a larger script it works fine.  For example, these both work:

--- begin file ---
<?php phpinfo(); ?>
---  end file  ---

--- begin file ---
<?
  phpinfo();
?>
---  end file  ---

The error I receive is a browser popup:  the URL (etc) has MIME type application/x-httpd-php.  Saving the file shows that it contains the php source.

This problem does not occur within the same set of files under a non-SSL enabled apache virtual host.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-05-15 14:37 UTC] sander@php.net 
Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem does not imply a bug in PHP itself.
For a list of more appropriate places to ask for help using PHP,
please visit http://www.php.net/support.php

Thank you for your interest in PHP.
 [2002-05-15 14:43 UTC] dave at dsb3 dot com 
I disagree.  A one-line test case (as provided within the documentation) that behaves differently from php4.2.0 and php4.2.1 would indicate a bug (or discrepancy) has snuck  into the code during the last release.

The fact it can be altered depending on whitespace within the file and whether running through an SSL enabled host is merely additional information I have provided to try to aide it's resolution.

I am not requesting support.  I am reporting that php's behaviour has been changed, in what appears to me to be a buggish fashion.
 [2002-06-27 20:05 UTC] sniper@php.net 
Please try this snapshot:

http://snaps.php.net/php4-latest.tar.gz

(I'm unable to reproduce this with it)
 [2002-07-28 01:00 UTC] php-bugs at lists dot php dot net 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Mon Feb 17 15:01:29 2025 UTC