http
http copied to clipboard
dart-lang
A composable API for making HTTP requests in Dart.
Tracking bug. This would make it easy to see how to do a client and a server.
This would be helpful to use in other custom server implementations.
Running `flutter pub run build_runner build --output=build` yields ``` [WARNING] ../../../../.pub-cache/hosted/pub.dev/http_parser-4.0.2/lib/src/case_insensitive_map.dart:10:37: Error: The class 'CanonicalizedMap' can't be extended outside of its library because it's a final class. class CaseInsensitiveMap extends...
I'm working on a code-gen package to improve the UX of creating backend apps. One of the primary use cases is to register acceptable MediaTypes for a given endpoint, and...
Hi. this types has `tryParse` option ``` int.tryParse(source) double.tryParse(source) DateTime.tryParse(formattedString) ``` It would be nice to have the same for `MediaType`
**Testing versions:** `4.0.2` and `c14fbf` **Steps to Reproduce:** 1. Find any instance of diaspora*, Mobilizon, Pleroma, Akkoma, Funkwhale or WriteFreely (you can use [Fediverse Observer](https://diaspora.fediverse.observer/list)) 2. Open `https:///.well-known/nodeinfo` 3. Take...
Due to JSON decode take 40.5ms on main isolate hence create a UI jank. Maybe we can move the decode function to a background isolate using the [compute](https://api.flutter.dev/flutter/foundation/compute-constant.html) function?
README.md still features WebSocketChannel as a feature, even though it was moved moved to [the web_socket_channel package](https://pub.dev/packages/web_socket_channel). Consider updating README to reflect that.
It's so crazy common to want to check this – and it's not super straight-forward. See https://github.com/google/googleapis.dart/blob/ec7b27cf3895c92b75ef407e1c109a9f7eba3a72/discoveryapis_commons/lib/src/utils.dart#L10-L16 https://github.com/GoogleCloudPlatform/functions-framework-dart/blob/80da6491efbf2e58a2c3f4732a3a7f055fe5eb37/functions_framework/lib/src/json_request_utils.dart#L39
When a response is received with the Content-Type header set to "application/json" (without specifying the charset) the parser incorrectly assumes the response to be encoded as ISO-8859-1 (Latin-1) The comments...
