[Rets-dev] RETS 1.x Cleanup: RETS GET transaction, HTTP 302 response, server-side actions

[Peter Williams]

In terms of issues to be address by the workgroup created in the last
RETS meeting, chartered to address RETS 1.x cleanup, Id propose that,
citing 1.7d6, 

A) text be added noting that a GET transaction may - upon performing its
server-side action - respond with a 302 Redirect. 

B) text be added noting that a RETS UA MAY/MUST follow that redirect to
another GET transaction URI for which the login transaction granted the
user access.

This is consistent with "3.1.3 Response Bodies - The body of a response
to most RETS requests is a well-formed XML document; the exceptions are
the Get transaction (section 8)...".





"CHAPTER 8
GET TRANSACTION

Gets an arbitrary file from the server or performs an arbitrary action,
specified by URI. This is a standard HTTP GET, per RFC 2616."





Can we clarify that 

1. a 302 Redirect is a valid response header, and that a RETS UA
MUST/SHOULD/MAY process a 302 Redirect?

2. Location is a valid response header, and that a RETS UA
MUST/SHOULD/MAY handle a Location normally (upon following a 302
Redirect, for example)?

3. the server-side action may be to invoke a server-side user agent
activity, such as an HTTP-GET or SOAP Request using HTTP or other
transport?

4. the server-side action invoking invoke an HTTP-GET or SOAP
server-side user agent activity MUST/SHOULD/MAY process a 302 Redirect
or SOAP Response Header equivalent?