As second in command of the SS and then Reichsfhrer-SS, Himmler was in regular contact with Hitler to arrange for SS men as bodyguards; Himmler was not involved with Nazi Party policy-making decisions in the years leading up to the seizure of power. From the late 1930s, the SS was independent of the control of other state agencies or government departments, and he reported only to Hitler.
Hitler's leadership style was to give contradictory orders to subordinates and to place them into positions where their duties and responsibilities overlapped with those of others. In this way, Hitler fostered distrust, competition, and infighting among his subordinates to consolidate and maximise his own power. His cabinet never met after 1938, and he discouraged his ministers from meeting independently. Hitler typically did not issue written orders, but gave them orally at meetings or in phone conversations; he also had Bormann convey orders. Bormann used his position to control the flow of information and access to Hitler, earning him enemies, including Himmler.
Hitler promoted and practised the Fhrerprinzip. The principle required absolute obedience of all subordinates to their superiors; thus Hitler viewed the government structure as a pyramid, with himselfthe infallible leaderat the apex. Accordingly, Himmler placed himself in a position of subservience to Hitler, and was unconditionally obedient to him. However, helike other top Nazi officialshad aspirations to one day succeed Hitler as leader of the Reich. Himmler considered Speer to be an especially dangerous rival, both in the Reich administration and as a potential successor to Hitler. Speer refused to accept Himmler's offer of the high rank of SS-Oberst-Gruppenfhrer, as he felt to do so would put him in Himmler's debt and obligate him to allow Himmler a say in armaments production.
Hitler called Himmler's mystical and pseudoreligious interests "nonsense". Himmler was not a member of Hitler's inner circle; the two men were not very close, and rarely saw each other socially. Himmler socialised almost exclusively with other members of the SS. His unconditional loyalty and efforts to please Hitler earned him the nickname of der treue Heinrich ("the faithful Heinrich"). In the last days of the war, when it became clear that Hitler planned to die in Berlin, Himmler left his long-time superior to try to save himself.
HTTP defines methods (sometimes referred to as verbs) to indicate the desired action to be performed on the identified resource. What this resource represents, whether pre-existing data or data that is generated dynamically, depends on the implementation of the server. Often, the resource corresponds to a file or the output of an executable residing on the server. The HTTP/1.0 specification defined the GET, POST and HEAD methods and the HTTP/1.1 specification added 5 new methods: OPTIONS, PUT, DELETE, TRACE and CONNECT. By being specified in these documents their semantics are well known and can be depended on. Any client can use any method and the server can be configured to support any combination of methods. If a method is unknown to an intermediate it will be treated as an unsafe and non-idempotent method. There is no limit to the number of methods that can be defined and this allows for future methods to be specified without breaking existing infrastructure. For example, WebDAV defined 7 new methods and RFC 5789 specified the PATCH method.
The GET method requests a representation of the specified resource. Requests using GET should only retrieve data and should have no other effect. (This is also true of some other HTTP methods.) The W3C has published guidance principles on this distinction, saying, "Web application design should be informed by the above principles, but also by the relevant limitations." See safe methods below.
The HEAD method asks for a response identical to that of a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content.
The POST method requests that the server accept the entity enclosed in the request as a new subordinate of the web resource identified by the URI. The data POSTed might be, for example, an annotation for existing resources; a message for a bulletin board, newsgroup, mailing list, or comment thread; a block of data that is the result of submitting a web form to a data-handling process; or an item to add to a database.
The PUT method requests that the enclosed entity be stored under the supplied URI. If the URI refers to an already existing resource, it is modified; if the URI does not point to an existing resource, then the server can create the resource with that URI.
The DELETE method deletes the specified resource.
The TRACE method echoes the received request so that a client can see what (if any) changes or additions have been made by intermediate servers.
The OPTIONS method returns the HTTP methods that the server supports for the specified URL. This can be used to check the functionality of a web server by requesting '*' instead of a specific resource.
The CONNECT method converts the request connection to a transparent TCP/IP tunnel, usually to facilitate SSL-encrypted communication (HTTPS) through an unencrypted HTTP proxy. See HTTP CONNECT tunneling.
The PATCH method applies partial modifications to a resource.
All general-purpose HTTP servers are required to implement at least the GET and HEAD methods, and, whenever possible, also the OPTIONS method.