P
Peter Judge
Guest
Q6. -mc should work with PASOE. Please log a bug if it doesn't. Q7. The HTTP client doesn't do anything special for Content-Encoding (either for requests or responses). Untested approach below but ... The OpenEdge.Net.HTTP.Filter.Payload.DefaultRequestFilter class is where you would add support for Content-Encoding for requests and for responses, in the OpenEdge.Net.HTTP.Lib.ABLSockets.ABLSocketLibrary class. In both cases it'd be in/after the ExtractEntity method. You could write a class that extends the above, and register them as the appropriate handlers. For requests OpenEdge.Net.HTTP.Filter.Writer.RequestWriterBuilder:Registry
ut('HTTP/1.1':u, get-class(Your.Class.That.Extends.DefaultRequestFilter)). For responses OpenEdge.Net.HTTP.Lib.ClientLibraryBuilder:Registryut(get-class(IHttpClientLibrary):TypeName, get-class(Your.Class.That.Extends.ABLSocketLibrary)). If you'd like to log a bug for this too, please do. It might end up being an enhancement but I'd think that it's worth logging. As I mentioned earlier, the PASOE server does the Content-Encoding in the Tomcat layer.
Continue reading...
ut('HTTP/1.1':u, get-class(Your.Class.That.Extends.DefaultRequestFilter)). For responses OpenEdge.Net.HTTP.Lib.ClientLibraryBuilder:Registryut(get-class(IHttpClientLibrary):TypeName, get-class(Your.Class.That.Extends.ABLSocketLibrary)). If you'd like to log a bug for this too, please do. It might end up being an enhancement but I'd think that it's worth logging. As I mentioned earlier, the PASOE server does the Content-Encoding in the Tomcat layer.Continue reading...