SOAP and Caching
When you submit a SOAP message it is always with an HTTP POST, even though the intent of the message may be to "get" data.
- So a cache server would not know from the HTTP method whether the client is doing a request.
A SOAP URI is always to the SOAP server, not to the actual target
- Consequently, a cache server would not know from the URI what resource is being requested.
Thus, with a SOAP message the cache server cannot determine (1) if data is being requested, nor (2) what resource is being requested.
- Conclusion: No caching possible with SOAP!
"I don’t know what is the target
resource. Furthermore, I don't
even know if the resource is
being requested. So, I must
forward the request. No caching"