[wp-hackers] HTTP status code on "Release not found" at wp.org

Robin Adrianse robin.adr at gmail.com
Sat Mar 10 04:04:31 GMT 2007

I think this is a good idea anyways. It is the equivalent of a 404 error,
just that the fancy rewriting script doesn't send a 404.

On 3/9/07, Alex Günsche <ag.ml2007 at zirona.com> wrote:
> Hi,
> this might be a question rather for the wp.org server admins, so I hope
> it's ok to post it here. I don't really know where to refer to, and I
> know that some of the responsible people read this list.
> I'm building a plugin which among other things downloads a given WP
> version from the URL http://wordpress.org/wordpress-XXX.zip using the
> Snoopy class. This works fine so far; only if one downloads a version
> that doesn't exist, it returns the string "Release not found. XXX" and
> -- here comes my problem -- HTTP status code 200.
> Of course, I could parse the string, but this is not very reliable. A
> better method would be a proper status code, preferably 404. Would that
> be possible?
> Regards,
> Alex
> --
> Alex Günsche, Zirona OpenSource-Consulting
> work: http://www.zirona.com/ | leisure: http://www.roggenrohl.net
> PubKey for this address: http://www.zirona.com/misc/ag.ml2007.asc
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list