Re: Update Center fails to parse updates.xml generated by maven based application

One thing I can think of to double-check:  There are two places encoding
can be specified for the updates.xml - the HTTP header, e.g.

Content-Type: text/xml; charset=UTF-8;

and then at the top of the XML itself, e.g.

<?xml version="1.0" encoding="utf-8" ?>

If they conflict, I'm not sure what the result would be.

You may want to look at the HTTP headers your server is sending and make
sure they both say the same thing, and say the right thing.

-Tim



On Thu, Mar 3, 2016 at 2:58 AM, Asterix45 <[email protected]> wrote:

> Hi Tim and thanks for your help.
>
> I've seen your GitHub, very very nice.
> I've developed my framework too and it's in PHP, I would like to use it
> also for the update center and I have to say that it works fine for other
> activities so I cannot see reason for not using it.
>
> I can say that xml is correctly encoded because I had private email with
> Arsi (he should be active on this forum too), he tested my xml and it works
> fine (he could see updates for my modules in his Update Center and that's
> good!).
> Also I checked my linux charset encoding to be sure I had no
> misconfiguration (obviously it was configured to UTF-8 [Rolling Eyes] ).
>
> Since I try to point to the file xml in my module (no PHP elaboration!)
> and it's fails too, I think I have some issue with the module itself.
>
> I restarted development of my nbm module from scratch and obtained same
> issue. I used the silently update code found online and that's could be the
> problem.
>
> Arsi gave me his code, this weekend I'll try it, also I'll try to use a
> standard Update Center, maybe I'll restart from scratch a new application
> only to test updates.
>
> Regards,
> Asterix
>
>
>
>
>


-- 
http://timboudreau.com