[
https://issues.apache.org/jira/browse/SHINDIG-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Brown closed SHINDIG-67.
------------------------------
Resolution: Won't Fix
This is no longer required in the spec. iGoogle is being more strict than it
needs to be today, but iGoogle is in the process of migrating this over to our
internal shindig deployment anyway. Content encoding is always determined from
the server's response headers (or else assumed to be utf-8). You can of course
continue including the declaration, but it is not required. This brings the
spec parsers into line with the XML standard, which do not require the xml
declaration.
> shindig does not complain if there is a missing xml header
> ----------------------------------------------------------
>
> Key: SHINDIG-67
> URL: https://issues.apache.org/jira/browse/SHINDIG-67
> Project: Shindig
> Issue Type: Bug
> Reporter: Martin Webb
>
> On a gadget with the following line missing:
> <?xml version="1.0" encoding="UTF-8" ?>
> gmodules.com responds with:
> Error parsing module spec: Not a properly formatted file missing xml header
> Shindig continues to render the gadget. The behaviour should be consistent.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
