This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5210 - Not valid soap response (not xml)
Summary: Not valid soap response (not xml)
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.8.2
Hardware: All All
: P2 normal
Target Milestone: 0.8.3
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-18 23:55 UTC by Karim
Modified: 2007-10-21 11:39 UTC (History)
0 users

See Also:


Attachments

Description Karim 2007-10-18 23:55:21 UTC
Hi,
When i try to validate this website http://titax.fr and retrieve the soap output, there's sevral erros in that output which make it not xml valid:
http://validator.w3.org/check?uri=http://titax.fr
Look at this error:
Line 913, Column > 80: XML Parsing Error: AttValue: " or ' expected. (see the > before 80?) 
this is reproduced in the soap output like this:

<m:error>
                <m:line>913</m:line>
                <m:col>> 80</m:col>   <<=== xml error occured here                                        
                <m:message>XML Parsing Error:  AttValue: &quot; or &#39; expected</m:message>
                <m:messageid>xmlwf</m:messageid>
                ...
</m:error>
Comment 1 Ville Skyttä 2007-10-19 14:59:22 UTC
Thanks for the report, fixed in CVS:
http://www.w3.org/mid/E1IitGN-00006v-5r%40lionel-hutz.w3.org
Comment 2 Karim 2007-10-19 17:47:41 UTC
(In reply to comment #1)
> Thanks for the report, fixed in CVS:
> http://www.w3.org/mid/E1IitGN-00006v-5r%40lionel-hutz.w3.org
> 

Thank you for the quick reply and fix! 
I think that the problem has its origins before the soap output generation actually, 
because you'll notice that the character > is also present in the html output:

Line 913, Column > 80: XML Parsing Error...

Look at Colum **>**. That should be 

Line 913, Column 80: XML Parsing Error...

Again thank you!
Comment 3 Ville Skyttä 2007-10-19 19:12:28 UTC
"Column > 80" is intentional, from the code:

    # working around an apparent odd limitation of libxml
    # which only gives context for lines up to 80 chars
    # http://www.w3.org/Bugs/Public/show_bug.cgi?id=4420
    # http://bugzilla.gnome.org/show_bug.cgi?id=424017

I don't see a problem with the HTML output, it is:

    <em>Line 913, Column &gt; 80</em>:

But there was a problem in ucn_output.tmpl, that's fixed in CVS now too.
Comment 4 Karim 2007-10-19 21:28:10 UTC
(In reply to comment #3)
> "Column > 80" is intentional, from the code:
> 
>     # working around an apparent odd limitation of libxml
>     # which only gives context for lines up to 80 chars
>     # http://www.w3.org/Bugs/Public/show_bug.cgi?id=4420
>     # http://bugzilla.gnome.org/show_bug.cgi?id=424017
> 
> I don't see a problem with the HTML output, it is:
> 
>     <em>Line 913, Column &gt; 80</em>:
> 

Justly, it's in that &gt; character. Look at 
http://validator.w3.org/check?uri=http://titax.fr

You'll notice that all other errors are in the form:
Line 949, Column 135: there is no attribute "border".
(Without that &gt; before the column number)
you see what I mean?

> But there was a problem in ucn_output.tmpl, that's fixed in CVS now too.
> 

Comment 5 Olivier Thereaux 2007-10-21 10:37:10 UTC
(In reply to comment #2)
> Line 913, Column > 80: XML Parsing Error...

The > is there to mention that the column is beyond 80.
This comes from a limitation of the XML parser.
Comment 6 Karim 2007-10-21 11:39:23 UTC
(In reply to comment #5)
> (In reply to comment #2)
> > Line 913, Column > 80: XML Parsing Error...
> 
> The > is there to mention that the column is beyond 80.
> This comes from a limitation of the XML parser.
> 

Ok, guys. Thank you for the information, I honnestly didn't knew that :)