Re: Make Beagle accesible from everywhere


On Tue, Jun 2, 2009 at 8:25 AM, j r <muxutzu hotmail com> wrote:
> I obtained a different answer depending on the URL call, and if I invoke the
> server from I receive an invalid XML string. For example:
> FROM HTTP:// (Invalid xml string)
> 391 // This number seems to be a random one

This looks like chunked transfer encoding to me.  This is part of the
HTTP 1.1 spec in which the server sends the number of bytes in a
chunk, followed by the chunk itself.  You might want to check the
headers if you can (with something like "curl -v") to see if this is
indeed the case.  If the client says that it's HTTP 1.1 it should know
how to deal with chunked transfer encoding.

> 1
> �

This, however, looks odd.  I'm not sure what that straggler byte is,
and that could be why the XML document is invalid, although it looks
like you also are receiving it from localhost below.

> AND FROM HTTP://localhost:4000 (Right XML string)
> <?xml version="1.0" encoding="utf-8"?>
> <ResponseWrapper xmlns:xsi="";
> xmlns:xsd="";>
>   <Message xsi:type="DaemonInformationResponse">
>     <Version>0.3.9</Version>
>     <SchedulerInformation TotalTaskCount="4" StatusString="Waiting on empty
> queue">
>       <PendingTasks />
>       <FutureTasks />
>       <BlockedTasks />
>     </SchedulerInformation>
>     <IndexStatus>
>       <QueryableStatus Name="Empathy" ItemCount="0" ProgressPercent="-1"
> IsIndexing="false" />
>       <QueryableStatus Name="Files" ItemCount="26495" ProgressPercent="-1"
> IsIndexing="true" />
>       <QueryableStatus Name="IndexingService" ItemCount="0"
> ProgressPercent="-1" IsIndexing="false" />
>       <QueryableStatus Name="GMailSearch" ItemCount="-1"
> ProgressPercent="-1" IsIndexing="false" />
>     </IndexStatus>
>     <IsIndexing>true</IsIndexing>
>   </Message>
> </ResponseWrapper>�

Why one request is receiving it that way and the other isn't, I have no idea.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]