ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darren Whitlen (JIRA)" <>
Subject [jira] [Commented] (RIPPLE-35) Ripple under Windows reads "config.xml" file, but claims it is missing or incorrect
Date Wed, 11 Sep 2013 21:34:53 GMT


Darren Whitlen commented on RIPPLE-35:

After fighting this for a while I've found that the issue comes down to the Content-Type header
the config.xml is served with.
Some HTTP servers may not have the correct mime-type for .xml files and will serve them incorrectly
causing the browsers XML parser to fail. When served with a correct text/xml mime type the
browser parses it correctly allowing Ripple to process it normally.

A better way to go about this is instead of using XMLHttpRequest.responseXML, use XMLHttpRequest.responseText
and parse it using DOMParser()'s parseFromString() function.
> Ripple under Windows reads "config.xml" file, but claims it is missing or incorrect
> -----------------------------------------------------------------------------------
>                 Key: RIPPLE-35
>                 URL:
>             Project: Apache Ripple
>          Issue Type: Bug
>         Environment: Windows 7 Home Edition, x86, Chrome browser (newest stable version),
Ripple Emulator extension for Chrome (newest stable version taken from Chrome Store).
>            Reporter: Tomasz Trejderowski
>            Priority: Minor
> Under Windows, Ripple Emulator always reports: "config.xml file could not be found in
application's root or is malformed XML", even though file is present at required location
(root) and is valid (PhoneGap Build builds applications using this file and don't comply about
anything wrong in it).
> According to some user, Chrome Dev Tools' Network Tab reports, that file is found and
requested by Ripple Emulator, so it shouldn't be a path or filename-related problem. Looks
more like file parsing problem.
> Details at Stack Overflow:
> Since Ripple seems to be working just fine, even without this file parsed, I marked this
bug as minor.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message