- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 83 for nossos (1.77 sec)
-
src/bytes/example_test.go
fmt.Printf("%s", bytes.Title([]byte("her royal highness"))) // Output: Her Royal Highness } func ExampleToTitle() { fmt.Printf("%s\n", bytes.ToTitle([]byte("loud noises"))) fmt.Printf("%s\n", bytes.ToTitle([]byte("брат"))) // Output: // LOUD NOISES // БРАТ } func ExampleToTitleSpecial() { str := []byte("ahoj vývojári golang") totitle := bytes.ToTitleSpecial(unicode.AzeriCase, str)
Registered: Tue Dec 30 11:13:12 UTC 2025 - Last Modified: Mon May 12 16:07:54 UTC 2025 - 16.5K bytes - Viewed (0) -
docs/pt/docs/deployment/https.md
Mas você pode configurar o servidor de aplicação para confiar nos cabeçalhos encaminhados enviados pelo proxy. Se você estiver usando o FastAPI CLI, pode usar a opção de CLI `--forwarded-allow-ips` para dizer de quais IPs ele deve confiar nesses cabeçalhos encaminhados.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Nov 12 16:23:57 UTC 2025 - 14.8K bytes - Viewed (0) -
docs/pt/docs/advanced/behind-a-proxy.md
Quando a **CLI do FastAPI** é configurada com `--forwarded-allow-ips`, ela confia nesses headers e os utiliza, por exemplo, para gerar as URLs corretas em redirecionamentos. ## Proxy com um prefixo de path removido { #proxy-with-a-stripped-path-prefix } Você pode ter um proxy que adiciona um prefixo de path à sua aplicação. Nesses casos, você pode usar `root_path` para configurar sua aplicação.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 17.2K bytes - Viewed (0) -
docs/pt/docs/deployment/manually.md
* Segurança - HTTPS * Executando na inicialização * Reinicializações * Replicação (o número de processos em execução) * Memória * Passos anteriores antes de começar
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Nov 12 16:23:57 UTC 2025 - 7.4K bytes - Viewed (0) -
docs/LICENSE
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL ORRegistered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Mon May 10 16:50:06 UTC 2021 - 18.2K bytes - Viewed (0) -
docs/pt/docs/tutorial/cors.md
* `http://localhost` * `https://localhost` * `http://localhost:8080` Mesmo se todos estiverem em `localhost`, eles usam diferentes protocolos ou portas, portanto, são "origens" diferentes. ## Passos { #steps }
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 5.9K bytes - Viewed (0) -
LICENSES/vendor/github.com/containerd/errdefs/pkg/LICENSE
Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Wed Mar 05 11:36:39 UTC 2025 - 10.7K bytes - Viewed (0) -
docs/pt/docs/tutorial/handling-errors.md
Pode ser que você precise comunicar ao cliente que: * O cliente não tem direitos para realizar aquela operação. * O cliente não tem acesso aquele recurso. * O item que o cliente está tentando acessar não existe. * etc. Nesses casos, você normalmente retornaria um **HTTP status code** próximo ao status code na faixa do status code **400** (do 400 ao 499).
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 10.2K bytes - Viewed (0) -
LICENSES/third_party/forked/libcontainer/LICENSE
Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Tue Oct 22 13:56:22 UTC 2024 - 10.5K bytes - Viewed (0) -
LICENSE
Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing
Registered: Sat Dec 20 11:21:39 UTC 2025 - Last Modified: Mon Jan 11 04:26:17 UTC 2021 - 11.1K bytes - Viewed (0)