> Project
> sipXecs
> New Revision
> 14086
> Committer
> xmlscott (Scott Lawrence)
> Date
> 2008-11-25 11:51:59 -0500 (Tue, 25
> Nov 2008)
>
> Log
>
>
> [XECS-1855] Added HttpFileAccess to sipXsupervisor (GET support for any file
> resource).
With this commit, we now have a new management interface in
sipXsupervisor. Any remote management application can now do an HTTP
GET request for any file known to the sipXsupervisor as a resource (this
includes all the current log files).
The request must be authenticated with TLS in the same way that the
XML-RPC is authenticated, and must be from one of the hosts listed in
the domain-config CONFIG_HOSTS directive (or the host on which the
sipXsupervisor is running).
The request URI must be the exact full path name of the file (while HTTP
allows this to be a full https URL including "https://<host>:<port>",
the sipXsupervisor interface doesn't support this).
If successful (indicated by an HTTP 200 response code), the file is
returned as the response body (the MIME type is set to
"application/octet-stream"). Because the server sends this with
HTTP/1.1 chunked encoding, it is safe to request arbitrarily large files
(unlike XML-RPC, which must encode the full contents in a string before
sending the response).
If unsuccessful (any other response code), the body will be an error
message (text/plain).
I added a new option to the 'sipxproc' command that uses this interface:
sipxproc --file /full/path/to-file
now returns the file on stdout.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
