C++ REST SDK VS libcurl

My favourite was Microsoft's cpprestsdk, but for some reason now is in maintenance mode, I don't know why, so it's hard to suggest it for new projects. A nice alternative is restc-cpp, that's has a good high-level interface, if this is what you want.

We also used https://github.com/microsoft/cpprestsdk but that isn't maintained- it was a pain working around the the different string sizes on different platforms

CppRestSDK is deprecated.

https://github.com/microsoft/cpprestsdk (concerned about being maintenance mode -> production?)

While it's not based on Boost Asio or Beast, Microsoft maintains a SDK for developing REST api's using C++, aptly named the C++ REST SDK. Here you can find the Github page. It pretty much covers everything you'd come to expect from a modern webserver package. It does come with a steep learning curve however.

I never thought I'd laud microsoft on open source software but this has certainly made my life easier... I mean come on, MIT licensed and everything...

https://github.com/microsoft/cpprestsdk

>But is it truly practical to use in 'higher-abstraction' apps like web or mobile?

Yes absolutely. Once you become familiar with the language the barrier is not that high. Familiarity trumps everything else.

That said, since i am not a Web/mobile developer i had collected some resources to help me learn how to use C++ for Web/Mobile apps, you may find it useful;

https://levelup.gitconnected.com/cross-platform-mobile-and-w...

https://github.com/Microsoft/cpprestsdk

https://medium.com/@ivan.mejia/modern-c-micro-service-implem...

I was starting a project that needs to read data with rest API and I'd like to use cpprestsdk from Microsoft. But it's readme says that's in maintenance mode and it's not recommended for new projects... I'd like to know why it's in maintenance mode, and if it will be abandoned. Also, if there's some equivalent library for cpp, instead of creating the business logic from scratch, i.e. with boost::beast.

So, if you're going that route, you can use one of the many HTTP wrappers around Boost::ASIO or something purpose-built like Pistache or Casablanca.

I'm not a fan of the "Reproducible tarballs" section, because it's explicitly about pre-processing the source code with autotools, instead of distributing a pure, unaltered git snapshot (which `git archive` can already generate in a deterministic way).

The section following then mentions signing the pre-processed source code, which I think is the wrong approach. It makes a difficult situation because of how strongly some people encourage signed source code, yet I think autotools is part of the build process and should run in the build server (and double checked by reproducible builds). If people pre-process the .orig.tar.xz they upload to Debian, this pre-processing won't be covered by reproducible builds because it happens undocumented.

The patch for "reproducible tarballs" is quite involved[0] and has rookie mistakes like "pin a specific container image using `@sha256:...` syntax, but then invoke `apt-get update` and `apt-get install` to install whatever Debian ships at that time".

[0]: https://github.com/curl/curl/pull/13250/files

Made a PR to curl in line with the above: https://github.com/curl/curl/pull/13338

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

This looks to be a general issue with curl.

On Windows by default it will also be checking the OS certificate store.

https://github.com/curl/curl/discussions/11707

This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.

I believe they have a bit of a point, as it isn’t locally obvious that randlen will match the zero-terminated length of randstr, at https://github.com/curl/curl/blob/1d8e8c9ad1ff3351386422535f.... It depends on the exact behavior and interface

This is an especially weird place to complain about length bounds checking, as no user-provided data is used here, and all the sizes are static at compile time. curl is putting a base64-encoded 16 byte random string (which turns into 25 ASCII bytes) into a static 40 byte buffer.

https://github.com/curl/curl/blob/1d8e8c9ad1ff3351386422535f...