An Open Source community for historical flight simulation.
https://seowhq.net/seowforum/
S` 4ShadesIV/JG7_4Shades wrote:Hi Hitcher,
I am expecting WTE_Goanna to submit new material for the Manchuria sector shortly. When that happens, I will release patches for SEDB31 and MP.
Cheers,
4Shades
Map side complete, just gotta get some data on railway stations and a couple of harbours. Should be ready to go by Friday, earlier if I take a day off work 
200 OK
The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:
GET an entity corresponding to the requested resource is sent in the response;
HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.
I am trying to think why *some* client browsers induce a 302 status and other clients induce a 200 status from the same server-side code.302 Found
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: RFC 1945 and RFC 2068 specify that the client is not allowed
to change the method on the redirected request. However, most
existing user agent implementations treat 302 as if it were a 303
response, performing a GET on the Location field-value regardless
of the original request method. The status codes 303 and 307 have
been added for servers that wish to make unambiguously clear which
kind of reaction is expected of the client.
And Glider too,he was a big help researching.IV/JG7_4Shades wrote:Wow.
OK, Kapt wins a box of Havanas.
