- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 1,370 for have (0.04 sec)
-
docs/en/docs/advanced/generate-clients.md
/// tip Notice the autocompletion for `name` and `price`, that was defined in the FastAPI application, in the `Item` model. /// You will have inline errors for the data that you send: <img src="/img/tutorial/generate-clients/image04.png"> The response object will also have autocompletion: <img src="/img/tutorial/generate-clients/image05.png"> ## FastAPI App with Tags
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 10.7K bytes - Viewed (0) -
docs/en/docs/tutorial/security/simple-oauth2.md
But `OAuth2PasswordRequestForm` is just a class dependency that you could have written yourself, or you could have declared `Form` parameters directly. But as it's a common use case, it is provided by **FastAPI** directly, just to make it easier. /// ### Use the form data /// tip
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 12.3K bytes - Viewed (0) -
cmd/erasure-healing-common.go
} for _, count := range vidMap { // do we have enough common versions // that have enough quorum to satisfy // the etag. if count >= quorum { return etags } } return make([]string, len(partsMetadata)) } // Extracts list of times from FileInfo slice and returns, skips // slice elements which have errors.
Registered: Sun Oct 27 19:28:09 UTC 2024 - Last Modified: Tue Oct 01 15:19:10 UTC 2024 - 12.6K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
# Security - First Steps Let's imagine that you have your **backend** API in some domain. And you have a **frontend** in another domain or in a different path of the same domain (or in a mobile application). And you want to have a way for the frontend to authenticate with the backend, using a **username** and **password**. We can use **OAuth2** to build that with **FastAPI**.
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 9.2K bytes - Viewed (0) -
docs/en/docs/tutorial/bigger-applications.md
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 18.4K bytes - Viewed (0) -
docs/en/docs/tutorial/security/oauth2-jwt.md
Using these ideas, JWT can be used for way more sophisticated scenarios. In those cases, several of those entities could have the same ID, let's say `foo` (a user `foo`, a car `foo`, and a blog post `foo`).
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sat Oct 26 11:45:10 UTC 2024 - 12.8K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
Now, from a **developer's perspective**, here are several things to keep in mind while thinking about HTTPS: * For HTTPS, **the server** needs to **have "certificates"** generated by a **third party**. * Those certificates are actually **acquired** from the third party, not "generated". * Certificates have a **lifetime**. * They **expire**. * And then they need to be **renewed**, **acquired again** from the third party.
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 12K bytes - Viewed (0) -
cmd/httprange.go
if sepIndex == -1 { return nil, fmt.Errorf("'%s' does not have a valid range value", rangeString) } offsetBeginString := byteRangeString[:sepIndex] offsetBegin := int64(-1) // Convert offsetBeginString only if its not empty. if len(offsetBeginString) > 0 { if offsetBeginString[0] == '+' { return nil, fmt.Errorf("Byte position ('%s') must not have a sign", offsetBeginString)
Registered: Sun Oct 27 19:28:09 UTC 2024 - Last Modified: Thu May 09 08:44:07 UTC 2024 - 5.9K bytes - Viewed (0) -
docs/en/docs/tutorial/body-multiple-params.md
```JSON { "item": { "name": "Foo", "description": "The pretender", "price": 42.0, "tax": 3.2 }, "user": { "username": "dave", "full_name": "Dave Grohl" } } ``` /// note Notice that even though the `item` was declared the same way as before, it is now expected to be inside of the body with a key `item`. ///
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 7.6K bytes - Viewed (0) -
docs/en/docs/tutorial/response-status-code.md
* **`300`** and above are for "Redirection". Responses with these status codes may or may not have a body, except for `304`, "Not Modified", which must not have one. * **`400`** and above are for "Client error" responses. These are the second type you would probably use the most. * An example is `404`, for a "Not Found" response.
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 4K bytes - Viewed (0)