[Grub-dev] Server answer codes
Yousef Ourabi
yourabi at zero-analog.com
Tue Jan 29 16:58:29 UTC 2008
i'm not sure 202 is the best for an error message regarding hbase -- section
6.1.1 of rfc 2616 is pretty clear that 2xx is success only -- while one
could make the argument that the "client" side was successful, I think a 5xx
would be more appropriate... since there was a problem, and it was clearly
on the server side...
input?
On 1/29/08, jer <jeremie at jabber.org> wrote:
>
> > 401 errors are most likely client errors. It means that the URLs
> > that were returned in the work unit don't match those that were sent
> > out. The URLs that are returned need to be in the same order as the
> > were in the work unit, and there can't be any missing.
>
> To be even more pedantic, if you are getting these it might help to
> understand exactly what it's validating. The hash code is generated
> by doing a cumulative:
>
> for each workunit entry
> hash = sha1hex( last-hash + " " + hostname + " " + path )
>
> The hostname and path that are placed into the resulting arc must be
> exactly the one in the given Host: header and path in the GET request
> line.
>
> It's important that we validate these to at least prevent URL
> injection through this API, that clients are only returning the URLs
> that they were assigned.
>
> Jer
>
> _______________________________________________
> Grub-dev mailing list
> Grub-dev at wikia.com
> http://lists.wikia.com/mailman/listinfo/grub-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/grub-dev/attachments/20080129/6af81a38/attachment.html
More information about the Grub-dev
mailing list