Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 83651 - after upgrade php is effectively disabled
Summary: after upgrade php is effectively disabled
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apache
Version: 7.2
Hardware: i686
OS: Linux
high
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brian Brock
URL: http://sitetest.athabascau.ca/my.php
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-06 19:44 UTC by Dmitry S. Makovey
Modified: 2007-03-27 04:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-06 21:38:53 UTC


Attachments (Terms of Use)

Description Dmitry S. Makovey 2003-02-06 19:44:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030129

Description of problem:
After I upgraded/fresh installed apache-1.3.27-1.7.2 for RH 7.2 or even the same
for RH 7.3 my php scripts are effectively disabled from precessing. they are
being sent as clear text.
Used packages:
apache-1.3.27-1.7.2
php-4.1.2-7.2.6

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. install RH 7.2
2. install newest apache rpm for it.
3. install newest php rpm for it.
4. try to run any php scripts after starting httpd    

Actual Results:  <?
 phpinfo();
?>

Expected Results:  loong-long page with current system info

Additional info:

it happened on my server with 7.2 and the same happened with my 7.3 at home.

Comment 1 Dmitry S. Makovey 2003-02-06 21:40:20 UTC
Figured out - php.ini by default now has "short_open_tag = Off" instead of "on"
which disables my scripts starting with "<?" instead of "<?php".


Note You need to log in before you can comment on or make changes to this bug.