title: why was HTTP status code 102 removed from HTTP/1.1
body: <p>returning status 102 for a REST service that might take a long time to complete seems like it might sometimes be a good idea.
  A better idea is often to return a 202 accepted with a reference to URLs with the status of the request and which will have the final answer when its ready.</p>
  <p>I note from <a href="https://evertpot.com/http/102-processing" rel="nofollow noreferrer">https://evertpot.com/http/102-processing</a> that status code 102 is not in the HTTP/1.1 spec (<a href="https://www.rfc-editor.org/rfc/rfc2616" rel="nofollow noreferrer">rfc2616</a>).
  <strong>Why was it removed?</strong></p>
  <p>And given that it has been why are many people still using and recommending it? Is it because most services must support HTTP/1.0 for backwards compatibility and therefore it is likely to be implemented anyway?</p>