No - it looks fine in OD.
I also changed the sending WMS to use plain ASCII instead of UTF-8 and
still won't work. Looks like I'm going to have to fetch the source and
debug it :-(
On 15 August 2013 15:48, Chris Snider <chris.sni...@issinc.com> wrote:
> Try checking the response in a hex editor and ensure the first character
> is really what is expected. We had a similar issue with a database GUI
> that was adding additional unprintable characters to the start of a dumped
> SQL file. Same thing may be occurring with the capabilities document.****
>
> ** **
>
> Chris Snider****
>
> Senior Software Engineer****
>
> ISS****
>
> ** **
>
> *From:* Ian Turton [mailto:ijtur...@gmail.com]
> *Sent:* Thursday, August 15, 2013 3:36 AM
> *To:* geoserver-users
> *Subject:* [Geoserver-users] cascading a GeoSever WMS fails****
>
> ** **
>
> I'm trying to cascade a remote GeoServer through a local one (mostly for a
> caching test) however I can't add the remote one as there is a problem
> parsing the capabilities request - though looking at it every thing seems
> fine (Notepad++ parses it fine and reports it as UTF-8 without BOM) but the
> error claims there is a problem with content in the prolog (line 1, char
> 1). The request is going through a http proxy but I don't think that is
> breaking things.****
>
> Can anyone suggest a fix?****
>
> cheers****
>
> Ian
> ****
>
>
> --
> Ian Turton****
>
--
Ian Turton
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
