- Sort Score
- Result 10 results
- Languages All
Results 221 - 230 of 2,010 for clients (0.04 sec)
-
docs/site-replication/gen-oidc-sts-cred.go
log.Fatalf("Please specify a MinIO server endpoint environment variable like:\n\n\texport MINIO_ENDPOINT=http://localhost:9000") } appParams := cmd.OpenIDClientAppParams{ ClientID: "minio-client-app", ClientSecret: "minio-client-app-secret", ProviderURL: "http://127.0.0.1:5556/dex", RedirectURL: "http://127.0.0.1:10000/oauth_callback", }
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Apr 29 01:27:09 UTC 2022 - 2.3K bytes - Viewed (1) -
docs/es/docs/how-to/separate-openapi-schemas.md
## No Separar Esquemas { #do-not-separate-schemas } Ahora, hay algunos casos donde podrías querer tener el **mismo esquema para entrada y salida**.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Tue Dec 16 16:33:45 UTC 2025 - 4.8K bytes - Viewed (0) -
docs/pt/docs/how-to/separate-openapi-schemas.md
Provavelmente, o principal caso de uso para isso é se você já tem algum código de cliente/SDK gerado automaticamente e não quer atualizar todo o código de cliente/SDK gerado ainda, você provavelmente vai querer fazer isso em algum momento, mas talvez não agora. Nesse caso, você pode desativar esse recurso no **FastAPI**, com o parâmetro `separate_input_output_schemas=False`. /// info | Informação
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Nov 12 16:23:57 UTC 2025 - 4.8K bytes - Viewed (0) -
src/main/java/jcifs/internal/SmbNegotiationRequest.java
/** * Interface for SMB protocol negotiation request messages. * Represents the client's request to negotiate SMB protocol version and capabilities * with the server, including security requirements like message signing. * * @author mbechler */ public interface SmbNegotiationRequest { /** * Checks whether SMB message signing is enforced by the client. * * @return whether SMB signing is enforced */Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 1.2K bytes - Viewed (0) -
docs/pt/docs/advanced/behind-a-proxy.md
Aqui está uma representação visual de como o **proxy** adiciona headers encaminhados entre o cliente e o **servidor da aplicação**: ```mermaid sequenceDiagram participant Client participant Proxy as Proxy/Load Balancer participant Server as FastAPI Server Client->>Proxy: HTTPS Request<br/>Host: mysuperapp.com<br/>Path: /items Note over Proxy: Proxy adds forwarded headersRegistered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 17.2K bytes - Viewed (0) -
internal/event/target/mqtt.go
} } return nil } // MQTTTarget - MQTT target. type MQTTTarget struct { initOnce once.Init id event.TargetID args MQTTArgs client mqtt.Client store store.Store[event.Event] quitCh chan struct{} loggerOnce logger.LogOnce } // ID - returns target ID. func (target *MQTTTarget) ID() event.TargetID { return target.id }Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Sep 06 23:06:30 UTC 2024 - 8.2K bytes - Viewed (0) -
docs/pt/docs/how-to/authentication-error-status-code.md
# Usar antigos códigos de status de erro de autenticação 403 { #use-old-403-authentication-error-status-codes } Antes da versão `0.122.0` do FastAPI, quando os utilitários de segurança integrados retornavam um erro ao cliente após uma falha na autenticação, eles usavam o código de status HTTP `403 Forbidden`.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 19:59:04 UTC 2025 - 1.3K bytes - Viewed (0) -
docs/es/docs/how-to/authentication-error-status-code.md
# Usar los códigos de estado antiguos 403 para errores de autenticación { #use-old-403-authentication-error-status-codes } Antes de FastAPI versión `0.122.0`, cuando las utilidades de seguridad integradas devolvían un error al cliente después de una autenticación fallida, usaban el código de estado HTTP `403 Forbidden`.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Tue Dec 16 16:16:35 UTC 2025 - 1.3K bytes - Viewed (0) -
cmd/sts-handlers_test.go
} // confirm that the user is able to access the bucket uClient := s.getUserClient(c, accessKey, secretKey, "") versions := c.mustUploadReturnVersions(ctx, uClient, bucket) c.mustNotDelete(ctx, uClient, bucket, versions[0]) assumeRole := cr.STSAssumeRole{ Client: s.TestSuiteCommon.client, STSEndpoint: s.endPoint, Options: cr.STSAssumeRoleOptions{ AccessKey: accessKey,
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Oct 15 17:00:45 UTC 2025 - 103.4K bytes - Viewed (1) -
docs/es/docs/advanced/behind-a-proxy.md
Aquí tienes una representación visual de cómo el **proxy** añade headers reenviados entre el cliente y el **application server**: ```mermaid sequenceDiagram participant Client as Cliente participant Proxy as Proxy/Load Balancer participant Server as Servidor de FastAPI Client->>Proxy: HTTPS Request<br/>Host: mysuperapp.com<br/>Path: /items Note over Proxy: El proxy añade headers reenviadosRegistered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 17.1K bytes - Viewed (0)