Nothing displays when creating XML pages and using a .php file as the XSL Template

RESOLVED INVALID

Status

()

--
major
RESOLVED INVALID
16 years ago
16 years ago

People

(Reporter: mpotte01, Assigned: peterv)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507

Nothing displays when creating XML pages and using a .php file as the XSL Template.

Here is the top of my XML page:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<?xml-stylesheet type="text/xsl" href="/sr2/xsl_sheets/xsl_sheet_01.php" ?>
Valid XML

Both my XML page and my XSL Both pages are dynamically created .php files and
are assigned the header: "Content-Type: text/xml"

If the XML and XSL are valid, the page doesn't load.  It just displays the
hourglass...

When opening each page separately (not linked) they both open correctly.  Page
info shows type is text/xml.  But when the XML is linked to the XSL sheet
nothing ever loads, you cannot view page source, and Page Info states that the
type is unknown.

Reproducible: Always

Steps to Reproduce:
1. Create an XML and XSL file using PHP, both with PHP extensions.
2. Open the XML File
3. Nothing shows!

Actual Results:  
A blank window with the hourglass.

Expected Results:  
Show the rendered XML file.

Again, if the XML is not linked to the XSLT, the XML shows properly.  The XSL
Template does as well.  The issue only occures when they are linked.
I also tried the headers Content-type: application/xml

Comment 1

16 years ago
please provide a testcase, we're not going to set up a webserver to test this
ourselves, sorry.

Comment 2

16 years ago
see #156676 comment#3.  Maybe this is the same thing that I have found when
creating xml via asp.  When I place the xsl file on the server and reference the
xsl template in the XML created by asp, I just get raw xml in the browser.

Comment 3

16 years ago
reporter, please provide a testcase. As Kevin pointed out, he had similar problems
and a server issue, make sure that you don't.
I'll INVALID this one on my next sweep of our UNCONFIRMED bugs, if we can't
reproduce it by then.

Comment 4

16 years ago
I have the same problem.

If i use the following .xml-file it's displayed correctly with Mozilla 1.4 RC1
on Suse linux V8.2, Mozilla 1.3.1 on Win2K and IE6.

<?xml version="1.0"
      encoding="ISO-8859-1"
      standalone="yes" ?>
<?xml-stylesheet type="text/xsl"
                 href="jr_data/jr.xsl"?>
 
<IntranetMainPage Title="jr">

</IntranetMainPage>

The following data is tranfered via http:

0000  3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31   <?xml version="1
0010  2e 30 22 0a 20 20 20 20 20 20 65 6e 63 6f 64 69   .0".      encodi
0020  6e 67 3d 22 49 53 4f 2d 38 38 35 39 2d 31 22 0a   ng="ISO-8859-1".
0030  20 20 20 20 20 20 73 74 61 6e 64 61 6c 6f 6e 65         standalone
0040  3d 22 79 65 73 22 20 3f 3e 0a 3c 3f 78 6d 6c 2d   ="yes" ?>.<?xml-
0050  73 74 79 6c 65 73 68 65 65 74 20 74 79 70 65 3d   stylesheet type=
0060  22 74 65 78 74 2f 78 73 6c 22 0a 20 20 20 20 20   "text/xsl".     
0070  20 20 20 20 20 20 20 20 20 20 20 20 68 72 65 66               href
0080  3d 22 6a 72 5f 64 61 74 61 2f 6a 72 2e 78 73 6c   ="jr_data/jr.xsl
0090  22 3f 3e 0a 20 0a 3c 49 6e 74 72 61 6e 65 74 4d   "?>. .<IntranetM
00a0  61 69 6e 50 61 67 65 20 54 69 74 6c 65 3d 22 6a   ainPage Title="j
00b0  72 22 3e 0a 0a 3c 2f 49 6e 74 72 61 6e 65 74 4d   r">..</IntranetM
00c0  61 69 6e 50 61 67 65 3e 0a                        ainPage>.



When i use the following .php file only IE6 displays it correct. The
Mozilla-Browsers displays nothing. They don't even asks for the .xsl files:

<?php print "<?xml version=\"1.0\"" ;?>
<?php print "             encoding=\"ISO-8859-1\"" ;?>
<?php print "       standalone=\"yes\" ?>" ;?>
<?php print "       <?xml-stylesheet type=\"text/xsl\"" ;?>
<?php print "                        href=\"jr_data/jr.xsl\"?>" ;?>
<IntranetMainPage Title="jr">
</IntranetMainPage>

And the following data is transferred via http to the browsers:

0000  31 33 0d 0a 3c 3f 78 6d 6c 20 76 65 72 73 69 6f   13..<?xml versio
0010  6e 3d 22 31 2e 30 22 0d 0a 32 32 0d 0a 20 20 20   n="1.0"..22..   
0020  20 20 20 20 20 20 20 20 20 20 65 6e 63 6f 64 69             encodi
0030  6e 67 3d 22 49 53 4f 2d 38 38 35 39 2d 31 22 0d   ng="ISO-8859-1".
0040  0a 31 61 0d 0a 20 20 20 20 20 20 20 73 74 61 6e   .1a..       stan
0050  64 61 6c 6f 6e 65 3d 22 79 65 73 22 20 3f 3e 0d   dalone="yes" ?>.
0060  0a 32 37 0d 0a 20 20 20 20 20 20 20 3c 3f 78 6d   .27..       <?xm
0070  6c 2d 73 74 79 6c 65 73 68 65 65 74 20 74 79 70   l-stylesheet typ
0080  65 3d 22 74 65 78 74 2f 78 73 6c 22 0d 0a 32 66   e="text/xsl"..2f
0090  0d 0a 20 20 20 20 20 20 20 20 20 20 20 20 20 20   ..              
00a0  20 20 20 20 20 20 20 20 20 20 68 72 65 66 3d 22             href="
00b0  6a 72 5f 64 61 74 61 2f 6a 72 2e 78 73 6c 22 3f   jr_data/jr.xsl"?
00c0  3e 0d 0a 33 32 0d 0a 3c 49 6e 74 72 61 6e 65 74   >..32..<Intranet
00d0  4d 61 69 6e 50 61 67 65 20 54 69 74 6c 65 3d 22   MainPage Title="
00e0  6a 72 22 3e 0a 3c 2f 49 6e 74 72 61 6e 65 74 4d   jr">.</IntranetM
00f0  61 69 6e 50 61 67 65 3e 0a 0d 0a 30 0d 0a 0d 0a   ainPage>...0....

I don't know whether the numbers (31, 22, ...) are the problem or not, but if
html-code is used instead of xml code all three browsers haven't any problem
with it and displays the .php-files correct. These numbers are created by PHP
V4.3.2 via Apache V2.0.46 for each <?php print-statements.
(Reporter)

Comment 5

16 years ago
Problem was discovered to be a dynamic picture build using JavaScript and not 
what was origionally thought.  I will create a test page when my server is 
back online.  
Josef: Those are not the complete http-transactions. The best thing would be if
you could provide the URL to your server so we can do debugging directly against it.

Comment 8

16 years ago
My next round is today. There is still no way to reproduce this, and I do suspect
a server config issue.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.