The bug was that you did not get it into the spec and so you have caused
considerable
confusion when cern allocated a different number for the meltdown case.
The meltdown case is needed in two very high volume cases of important
fielded servers.
I have changed the error code returned from 502 issued by CERN early this
fall to
your PC 503. Let us not have another big round of confusion here again.
The only way we're going to avoid further confusion is with different error
codes.
So, let us stick with 503 to mean melting down don't try back soon unless I
give you
a time.
Let us add a new error code 504 (?) for use with all administrative cases,
e.g. down for maintanance
back whenever.....
Since a server that is melting down has no cycles to spare, it needs to do
minimum work to
issue the error code. For this reason, all the nice administrative frills
need to be added to
a separate error code.
We should get a decision on this and get it into the 2.0 http spec so that
2.0 compliant servers
and clients do reasonable things in these denial of service cases.
John C. Mallery
Artificial Intelligence Laboratory
Massachusetts Institute of technology
545 Technology Square, NE43-797
Camridge, MA 02139 USA
URL: http://www.ai.mit.edu/people/jcma/jcma.html