« Return to Thread: HTTP 202 Status Code
Re: HTTP 202 Status Code
by Karel Vervaeke
::
Rate this Message:
The only 202 response explicitly returned in Daisy is in the
HttpConnector - it's impossible to tell what went wrong just from that
status code.
The body of the http response should tell you more (and so should the
log files if I'm not mistaken).
HTH,
Karel
On Fri, Jun 19, 2009 at 8:30 PM, Eric Ranschau<ERanschau@...> wrote:
>
> Hi all,
>
> I'm having an issue with the Daisy Repo. Server I'm hoping someone can shed
> some light on. I have written a small Java application that basically scans
> the repository for documents of a specified type; images and videos in this
> case. The application then reads the binary data out and creates a copy of
> the file on a web-accessible folder on a server. All has been going well
> until today when the part mirroring application started receiving an HTTP
> 202 status code when requesting the assets by the URL (ex:
> http://localhost:9263/repository/document/6512-[redacted]/version/last/part/ImageData/data?branch=main&language=default).
> This appears to be occurring on all assets, not just newly created ones.
>
> Has anyone seen this kind of behavior when retrieving content in this
> manner?
>
> Eric Ranschau
> Development Manager
>
> e: eranschau@...
> p: 612 215 9832
> f: 612 215 9801
> c: 612 877 0391
>
> OLSON
> We Think in Social Circles
> www.oco.com
>
>
> ___________________________________________
> This email has been scanned by MessageLabs.
> ___________________________________________
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy
HttpConnector - it's impossible to tell what went wrong just from that
status code.
The body of the http response should tell you more (and so should the
log files if I'm not mistaken).
HTH,
Karel
On Fri, Jun 19, 2009 at 8:30 PM, Eric Ranschau<ERanschau@...> wrote:
>
> Hi all,
>
> I'm having an issue with the Daisy Repo. Server I'm hoping someone can shed
> some light on. I have written a small Java application that basically scans
> the repository for documents of a specified type; images and videos in this
> case. The application then reads the binary data out and creates a copy of
> the file on a web-accessible folder on a server. All has been going well
> until today when the part mirroring application started receiving an HTTP
> 202 status code when requesting the assets by the URL (ex:
> http://localhost:9263/repository/document/6512-[redacted]/version/last/part/ImageData/data?branch=main&language=default).
> This appears to be occurring on all assets, not just newly created ones.
>
> Has anyone seen this kind of behavior when retrieving content in this
> manner?
>
> Eric Ranschau
> Development Manager
>
> e: eranschau@...
> p: 612 215 9832
> f: 612 215 9801
> c: 612 877 0391
>
> OLSON
> We Think in Social Circles
> www.oco.com
>
>
> ___________________________________________
> This email has been scanned by MessageLabs.
> ___________________________________________
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy
« Return to Thread: HTTP 202 Status Code
| Free embeddable forum powered by Nabble | Forum Help |
