Entry | |||
---|---|---|---|
R0 | Pointer to the name of non-standard HTTP method | ||
R1 | Method flags | ||
Bits 0-1 => | 0= Caller must set up everything | ||
1= Behave like PUT/POST | |||
2= Behave like GET | |||
3= Unused | |||
Bits 2-31 => | Reserved. Must be zero |
Exit | |
---|---|
R2 | Opaque method number to pass in R2 in calls to URL_GetURL |
AcornHTTP is designed to be very flexible but it is limited to the classical HTTP methods.
Since its original design a couple of other HTTP methods have been defined for various purposes e.g. for WebDAV, CalDAV etc. which are more or less popular. Many methods are in fact similar to the standard set (GET/PUT etc) and so can be handled by changing AcornHTTP quite simply.
Every client which wants to use AcornHTTP with a non-standard HTTP method registers the method details via this SWI.
When a client no longer makes usage of the registered HTTP non-standard method especially when quitting it has to deregister its method(s). This allows other applications to reuse the method number for their own purposes.
Any number in method range 1-127 may be returned as a valid result except the method numbers which are assigned to HTTP standard methods (GET, HEAD, POST, PUT, OPTIONS, TRACE, DELETE).