http-client, branch 2.0Http-client is a highlevel HTTP client library written in pure Scheme.
https://code.more-magic.net/http-client/atom?h=2.02024-09-13T17:50:03ZPort http-client to CHICKEN 62024-09-13T17:50:03ZPeter Bexpeter@more-magic.net2024-09-13T17:50:03Zurn:sha1:299eef8c087b48de8609f6b66d2d31d17dc0cc37Tag 1.2.22024-06-28T12:44:33ZPeter Bexpeter@more-magic.net2024-06-28T12:44:33Zurn:sha1:36f623a790d1cc90534dfdd3a0a4ffc3f64977a3Check for closed ports when writing chunks and give a hint to the user2024-06-28T07:04:48ZPeter Bexpeter@more-magic.net2024-06-28T07:04:48Zurn:sha1:8f92a6c32da01150400261515d3a4aa8a6ac4470
This makes it a bit more obvious what happened in cases like #1838,
reported by Woodrow E Douglass.
While at it, add some more test cases for this particular case, but
also for retry-attempts, as this is also affected when retry is
allowed for non-idempotent requests (which is pretty uncommon, but
possible)
Allow raw string data instead of file for multipart content (#1838)2024-06-27T13:51:26ZPeter Bexpeter@more-magic.net2024-06-27T13:50:55Zurn:sha1:64563b82ae1ddc87900aebad34529516f34657f7
This allows one to pass in a filename for the data.
Fix broken test for string ports2024-06-27T13:36:56ZPeter Bexpeter@more-magic.net2024-06-27T13:36:56Zurn:sha1:ff0aa990d5064b70f2bfa50f0f6f3b007048d6ff
For some reason the hardcoded length was incorrect. It makes more
sense to not hardcode it, as the exact value might differ depending on
the boundary etc.
Try to determine multipart content length for string ports2022-03-15T07:08:46ZPeter Bexpeter@more-magic.net2022-03-15T07:08:46Zurn:sha1:a4c631332faaf7506f8cc9443c22deb7db2b4335
This makes it slightly more reliable for certain servers which
absolutely require content length.
An alternative would be to have an explicit API for sending static
string contents. This could be in addition to this approach, because
this should always be a net win.
Drop redundant stripping of directory name when sending files2022-02-23T07:31:58ZPeter Bexpeter@more-magic.net2022-02-23T07:31:58Zurn:sha1:cd301f3a86e15de48d122b112c1f16fa5b316e3f
As pointed out by Siiky, intarweb already strips the directory name,
so we don't have to do it here. Allows us to drop an import, which
is always nice for clarity.
Also update the copyright year.
Tag 1.2.12021-09-10T05:11:18ZPeter Bexpeter@more-magic.net2021-09-10T05:11:18Zurn:sha1:ba310f212a77df2056dc718fba3be2479d892ef9Work around "fake" empty path by uri-common (#1448)2021-09-06T05:59:43ZPeter Bexpeter@more-magic.net2021-09-06T05:56:05Zurn:sha1:4c324413206ee42f4611b50a86529d096d63dbaf
When we check to see if the underlying path must be updated
to be present, we should know that uri-common is faking a
path of (/ "") when the path is empty.
The path normalization in uri-common could use some work though,
as it never really touches the underlying uri-generic object.
On the other hand, this is sort of the promise that uri-common
tries to make - it never mangles the uri object unless you explicitly
update something yourself.
Also mangle the path when sending to a proxy2021-09-03T14:12:38ZPeter Bexpeter@more-magic.net2021-09-03T14:12:34Zurn:sha1:f3efa21fb78688b92022304bbb486f7c4eb3b7bb
That path should also have a trailing slash just like when
requesting a regular URI. See #1781