@@ -134,7 +134,7 @@ requests.post("https://httpbin.org/post", data = java.nio.file.Paths.get("thing.
134
134
```
135
135
136
136
The ` data ` parameter also supports anything that implements the
137
- [ Writable] ( https://github.com/lihaoyi/geny#writable ) interface, such as
137
+ [ Writable] ( https://github.com/com- lihaoyi/geny#writable ) interface, such as
138
138
[ ujson.Value] ( http://com-lihaoyi.github.io/upickle/#uJson ) s,
139
139
[ uPickle] ( http://com-lihaoyi.github.io/upickle ) 's ` upickle.default.writable ` values,
140
140
or [ Scalatags] ( http://com-lihaoyi.github.io/scalatags/ ) 's ` Tag ` s
@@ -184,8 +184,8 @@ Requests exposes the `requests.get.stream` (and equivalent
184
184
perform streaming uploads/downloads without needing to load the entire
185
185
request/response into memory. This is useful if you are upload/downloading large
186
186
files or data blobs. ` .stream ` returns a
187
- [ Readable] ( https://github.com/lihaoyi/geny#readable ) value, that can be then
188
- passed to methods like [ os.write] ( https://github.com/lihaoyi/os-lib#oswrite ) ,
187
+ [ Readable] ( https://github.com/com- lihaoyi/geny#readable ) value, that can be then
188
+ passed to methods like [ os.write] ( https://github.com/com- lihaoyi/os-lib#oswrite ) ,
189
189
` fastparse.parse ` or ` upickle.default.read ` to handle the received data in a
190
190
streaming fashion:
191
191
@@ -215,7 +215,7 @@ too big to fit in memory, while still benefiting from most of Requests' friendly
215
215
216
216
Requests does not provide any built-in JSON support, but you can easily use a
217
217
third-party JSON library to work with it. This example shows how to use
218
- [ uJson] ( http ://www. lihaoyi.com /upickle/) talk to a HTTP endpoint that requires a
218
+ [ uJson] ( https ://com- lihaoyi.github.io /upickle/) talk to a HTTP endpoint that requires a
219
219
JSON-formatted body, either using ` upickle.default.stream ` :
220
220
221
221
``` scala
@@ -254,7 +254,7 @@ json.arr(0).obj.keys
254
254
255
255
While Requests-Scala doesn't come bundled with JSON functionality, it is trivial
256
256
to use it together with any other 3rd party JSON library (I like
257
- [ uJson] ( http ://www.lihaoyi. com/upickle/ ) ) So just pick whatever library you
257
+ [ uJson] ( https ://github. com/com-lihaoyi/upickle ) ) So just pick whatever library you
258
258
want.
259
259
260
260
## Multipart Uploads
@@ -532,7 +532,7 @@ r2.text
532
532
There is a whole zoo of HTTP clients in the Scala ecosystem. Akka-http, Play-WS,
533
533
STTP, HTTP4S, Scalaj-HTTP, RosHTTP, Dispatch. Nevertheless, none of them come
534
534
close to the ease and weightlessness of using Kenneth Reitz's
535
- [ Requests] ( http ://docs.python- requests.org /) library: too many implicits,
535
+ [ Requests] ( https ://requests.readthedocs.io/en/latest /) library: too many implicits,
536
536
operators, builders, monads, and other things.
537
537
538
538
When I want to make a HTTP request, I do not want to know about
@@ -657,7 +657,7 @@ request is just a function call that takes parameters; that is all you need to
657
657
know.
658
658
659
659
As it turns out, Kenneth Reitz's Requests is
660
- [ not a lot of code] ( https://github.com/requests/requests/tree/master /requests ) .
660
+ [ not a lot of code] ( https://github.com/requests/requests/tree/main /requests ) .
661
661
Most of the heavy lifting is done in other libraries, and his library is a just
662
662
thin-shim that makes the API 10x better. It turns out on the JVM most of the
663
663
heavy lifting is also done for you, by ` java.net.HttpUrlConnection ` in the
0 commit comments