| Age | Commit message (Collapse) | Author |
|---|
|
Not just the domain name. This gives better HTTP 1.0 examples if someone
wants to copy them.
Signed-off-by: Damien George <damien@micropython.org>
|
|
`ssl.wrap_socket()` is deprecated in CPython, so use `SSLContext` instead,
so the example is a good example to copy.
Signed-off-by: Damien George <damien@micropython.org>
|
|
The main changes here are to pass the address family and socket type to
`getaddrinfo()`, and then use the result of the address lookup when
creating the socket, so it has the correct address family.
This allows both IPv4 and IPv6 to work, because the socket is created with
the correct AF_INETx type for the address.
Also add some more comments to the examples to explain what's going on.
Fixes issue #15580.
Signed-off-by: Damien George <damien@micropython.org>
|
|
Non-blocking SSL streams can be difficult to get right, so provide a
working example, of a HTTPS client.
Signed-off-by: Damien George <damien@micropython.org>
|
|
It's better for discoverability to have these examples named `https_xxx.py`
rather than `http_xxx_ssl.py`.
Signed-off-by: Damien George <damien@micropython.org>
|
|
Applies to drivers/examples/extmod/port-modules/tools.
This work was funded through GitHub Sponsors.
Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
|
|
This fixes ruff rule F841.
|
|
This is run with uncrustify 0.70.1, and black 19.10b0.
|
|
This example will now work on all ports with networking and ssl support,
with both axtls and mbedtls.
|
|
|
|
|
|
|
|
Name recv() based a "simplistic", as it can't work robustly in every
environment. All this is to let people concentreate on proper, read()-
based one (and to turn recv() based into a "negative showcase",
explaining what are the pitfalls of such approach).
|
|
Otherwise, on bare-metal/RTOS systems can lead to resource leaks.
|
|
Since "read-exactly" stream refactor, where stream.read(N) will read
exactly N bytes (unless EOF), http_server* examples can't any longer do
client_socket.read(4096) and expect to get full request (it will block
on HTTP/1.1 client). Instead, read request line by line, as the HTTP
protocol requires.
|
|
Instead of extracting 4th element, extact last. Much easier to remember!
|
|
|
|
|
|
This is helpful when running on deeply embedded targets, but may be
"security risk". Caveat emptor.
|
|
Allows to re-run code if it was imported as a module (e.g., on bare-metal
ports).
|
|
|
|
Allows to re-run code if it was imported as a module (e.g., on bare-metal
ports).
|
|
|
|
|
|
|
