</p>

<p>
For example,
</p>

<pre>
DATA divtab&lt;&gt;+0x00(SB)/4, $0xf4f8fcff
DATA divtab&lt;&gt;+0x04(SB)/4, $0xe6eaedf0
...
DATA divtab&lt;&gt;+0x3c(SB)/4, $0x81828384
GLOBL divtab&lt;&gt;(SB), RODATA, $64

GLOBL runtime·tlsoffset(SB), NOPTR, $4
</pre>

<p>
declares and initializes <code>divtab&lt;&gt;</code>, a read-only 64-byte table of 4-byte integer values,

	MOVL CR0, DX // 0f20c2
	MOVL CR4, DI // 0f20e7
	MOVL AX, CR0 // 0f22c0
	MOVL DX, CR0 // 0f22c2
	MOVL DI, CR4 // 0f22e7
	MOVL DR0, AX // 0f21c0
	MOVL DR6, DX // 0f21f2
	MOVL DR7, SI // 0f21fe
	// Test other movtab entries.
	PUSHL SS // 16
	PUSHL FS // 0fa0
	POPL FS  // 0fa1
	POPL SS  // 17

	RDPID AX                                // f30fc7f8

	// End of tests.

				"application/dec-dx",
				"application/dialog-info+xml",
				"application/dicom",
				"application/dita+xml",
				"application/dita+xml;format=map",
				"application/dita+xml;format=topic",
				"application/dita+xml;format=task",
				"application/dita+xml;format=concept",
				"application/dita+xml;format=val",
				"application/dns",
				"application/dvcs",
				"application/ecmascript",

#### Esquema de la API { #api-schema }

En este caso, <a href="https://github.com/OAI/OpenAPI-Specification" class="external-link" target="_blank">OpenAPI</a> es una especificación que dicta cómo definir un esquema de tu API.

Esta definición de esquema incluye los paths de tu API, los posibles parámetros que toman, etc.

#### Esquema de Datos { #data-schema }

    <sub-class-of type="application/dita+xml"/>
    <_comment>DITA Task Topic</_comment>
    <root-XML localName="task"/>
    <root-XML localName="task" namespaceURI="http://docs.oasis-open.org/namespace"/>
  </mime-type>
  <mime-type type="application/dita+xml;format=concept">
    <sub-class-of type="application/dita+xml;format=topic"/>
    <_comment>DITA Concept Topic</_comment>
    <root-XML localName="concept"/>

Após isso, o cliente e o servidor possuem uma conexão TCP encriptada, que é provida pelo TLS. E então eles podem usar essa conexão para começar a comunicação HTTP propriamente dita.

E isso resume o que é HTTPS, apenas HTTP simples dentro de uma conexão TLS segura em vez de uma conexão TCP pura (não encriptada).

/// tip | Dica

	MOVQ CR0, DX // 0f20c2
	MOVQ CR4, DI // 0f20e7
	MOVQ AX, CR0 // 0f22c0
	MOVQ DX, CR0 // 0f22c2
	MOVQ DI, CR4 // 0f22e7
	MOVQ DR0, AX // 0f21c0
	MOVQ DR6, DX // 0f21f2
	MOVQ DR7, SI // 0f21fe
	// Test other movtab entries.
	PUSHQ GS // 0fa8
	PUSHQ FS // 0fa0
	POPQ FS  // 0fa1
	POPQ GS  // 0fa9
	// All instructions below semantically have unsigned operands,
	// but previous assembler permitted negative arguments.

found in the LICENSE file. // Package ssh implements the SSH KDF as specified in RFC 4253, // Section 7.2 and allowed by SP 800-135 Revision 1. package ssh import ( "crypto/internal/fips140" _ "crypto/internal/fips140/check" ) type Direction struct { ivTag []byte keyTag []byte macKeyTag []byte } var ServerKeys, ClientKeys Direction func init() { ServerKeys = Direction{[]byte{'B'}, []byte{'D'}, []byte{'F'}} ClientKeys = Direction{[]byte{'A'}, []byte{'C'}, []byte{'E'}} } func Keys[Hash fips140.Hash](hash...

license that can be found in the LICENSE file. // Package ssh implements the SSH KDF as specified in RFC 4253, // Section 7.2 and allowed by SP 800-135 Revision 1. package ssh import ( _ "crypto/internal/fips140/check" "hash" ) type Direction struct { ivTag []byte keyTag []byte macKeyTag []byte } var ServerKeys, ClientKeys Direction func init() { ServerKeys = Direction{[]byte{'B'}, []byte{'D'}, []byte{'F'}} ClientKeys = Direction{[]byte{'A'}, []byte{'C'}, []byte{'E'}} } func Keys[Hash hash.Hash](hash...