Q:

HTTP status code in REST API for using GET to query a “Not Ready Yet, Try Again Later” resource? 

First of all, I've read some relevant posts:

Best HTTP status code in REST API for “Not Ready Yet, Try Again Later”?  It is about GET an item
Is it wrong to return 202 “Accepted” in response to HTTP GET?  It is about GET an item
HTTP Status Code for Resource not yet available It is about POST
HTTP status code for in progress?  It is about GET but no clear answer. 

but I still think I should raise my question and my thoughts here.  What should be the HTTP status code in REST API for using GET to QUERY a “Not Ready Yet, Try Again Later” resource?  For example, client tries to query all local news happen in future(!)  by make an HTTP GET to this url: http://example.com/news?city=chicago&date=2099-12-31 so what shall the server reply? 
These are the http status code I considered, their rfc definition and why I am not fully satisfied with:

3xx Redirection.  Comment: Not an option because there is no other link to be redirected to. 
503 Service Unavailable: The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.  The implication is that this is a temporary condition which will be alleviated after some delay.  If known, the length of the delay MAY be indicated in a Retry-After header.  Comment: The retry behavior is desired, but semantically the situation is not server's fault at all, so all 5xx look weird. 
4xx Client Error.  Comment: Looks promising.  See below. 
413 Request Entity Too Large: The server is refusing to process a request because the request entity is larger than the server is willing or able to process. ...  If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again.  Comment: The retry behavior is desired, however the "Entity Too Large" part is somewhat misleading. 
417 Expectation Failed: The expectation given in an Expect request-header field (see section 14.20) could not be met by this server.  Comment: So it should be caused by an Expect request-header, not applicable to my case. 
406 Not Acceptable: The resource ... not acceptable according to the accept headers sent in the request.  Comment: so it is caused by the Accept request-header, not applicable to my case. 
409 Conflict: The request could not be completed due to a conflict with the current state of the resource.  This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. ...  Conflicts are most likely to occur in response to a PUT request.  Comment: This one is close.  Although my case is not about PUT, and isn't actually caused by conflict. 
404 Not Found: The server has not found anything matching the Request-URI.  Comment: Technically, my url path (http://example.com/news) DOES exist, it is the parameters causing problems.  In this case, returning an empty collection instead of a 404, is probably more appropriate. 
403 Forbidden: The server understood the request, but is refusing to fulfill it.  Authorization will not help and the request SHOULD NOT be repeated.  Comment: Generally this is supposed to be used in any restricted resource? 
400 Bad Request: The request could not be understood by the server due to malformed syntax.  The client SHOULD NOT repeat the request without modifications.  Comment: It is not true in my case.  My server understands the request, its syntax is good, only the meaning is bad. 
2xx Successful.  Comment: If 4xx doesn't work, how about 2xx?  See below. 
200 OK.  Comment: Fine.  So what should I include in the response body?  null or [] or {} or {"date": "2099-12-31", "content_list": null} or ... which one is more intuitive?  On the other hand, I prefer a way to clearly differentiate the minor "future news" error from the more common "all query criteria are good, just no news this day" situation. 
202 Accepted: The request has been accepted for processing, but the processing has not been completed.  The request might or might not eventually be acted upon.  Comment: Providing that we can use 202 in a GET request, it is acceptable.  Then refer to the 200 comment. 
204 No Content: The server has fulfilled the request but does not need to return an entity-body.  Comment: Providing that we can use 204 in a GET request, it is acceptable.  Just don't know whether this is better than 202 or 200. 
More on 2xx: Comment: I assume all 2xx response will likely be cached somewhere.  But in my case, if I return an empty body for "tomorrow's news", I don't want it to be cached.  Ok, explicitly specify the "no cache" headers should help.  

Your thoughts? 

A:

Use 404. 
Your objection to it is based on a popular understanding of a URI as not including the querystring. " Because I have multiple URI's that map to the same handler," goes the logic, "my resource does in fact exist and is just being parameterized by querystring args." 
This is incorrect.  As the URI spec itself says in Section 3.3 (emphasis mine),

"The path component contains data, usually organized in hierarchical
  form, that, along with data in the non-hierarchical query
  component (Section 3.4), serves to identify a resource within the
  scope of the URI's scheme and naming authority (if any)." 

Resources are identified by URI's, and any change to any part of an absolute-URI identifies a separate resource.  Tweet that to everyone you know once a day until they tell you to stop.  Therefore a 404 is a perfect match: "The 404 (Not Found) status code indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists."  

A:

You are retrieving the news for that day, which is a valid day, there just isn't any news.  A 200 response of an empty body, or a what ever makes sense based on the mediatype would seem the logical.  This depends on the media type you have decided with the client. 
404 would make more sense if the date format was wrong (you asked for the 45th day of November, or asked for a city that doesn't exist.) 
As an aside the URL would be better in the format http://example.com/news/chicago/2099-12-31 since that is the specific resource you want to retrieve.  This format would make things like 404s clearer as well.