I implement a bittorrent client using libtorrent. but I meet a problem. I have a http file server as the web seed. The server just support digest authentication for http request. and Libtorrent support basic auth by default. Does it have any way to make libtorrent to support digest auth? It would be nice to give an example. Thanks in advance.
no, libtorrent does not support digest authentication for HTTP seeds.
Patches are welcome! (and really, web servers and HTTP trackers should really be transitioned to use boost.beast instead of a homegrown HTTP parser)
Related
I have a client written by C, it uses libcurl to send json to a restful api service(say it server). The server was written by java, the restful api was implemented by jersey, one of JAX-RS( It's very simple and can switch to another JAX-RS implementation). Now I want to do some security work between the C client access to the java restful api server. I searched on the Internet that seems I should use kerberos or spnego for the HTTP access. I met some problem.
I want to use kerberos/spnego authentication. But I look through the security part of jersey doc (https://jersey.java.net/documentation/latest/security.html) and I didn't found any kerberos related doc. Do you know whether jersey support kerberos ?
If I switch to Apache CXF,is it easy to switch ? I checked the doc about CXF kerberos support. Looks like it's too simple, do you have any detail doc or simple example to support kerberos authentication when using Apache CXF ?
If there is anything wrong, please correct me. Thanks.
This is achievable with Jersey. Jersey Client uses ClosableHttpClient in its implementation.
If you want to use SPNEGO authentication scheme for Kerberos, you may have to write a custom Connector and ConnectorProvider [ I haven't found a way to set AuthenticationScheme with ApacheConnector].
Check this post too for reference if it solves your usecase Can JCIFS be used with Jersey? :)
I'm using gSOAP with EWS via proxy services to connect to Exchange services. I've fully working C++ gSOAP code for sending message on Windows, but when I compile and run the same code on Ubuntu, I've got 401 Unauthorized Error, Why?
On Windows:
I've used the binaries of soapcpp2.exe and wsdl2h.exe to generate header files etc.
For compile and run: I'm using MobaXterm (a kind of Terminal)
Please anyone who are familiar with gSOAP help me to figure out the possible problem. Many thanks in advance.
The 401 Unauthorized Error requires HTTP authentication, either with HTTPS and basic authentication or with HTTP digest authentication. The proxy also likely requires authentication.
See the tutorial on HTTP Digest Authentication
After installing google-api-client library for C++ on a Fedora 20 machine, I find out that it has external dependencies on libcurl (for example, setting up http proxy). I was planning to use google-api-client for sending HTTP request, mainly, HTTP multipart POST request. However, libcurl does provide support for multipart HTTP POST request also.
Could someone let me know the advantages of using Google API Client library for C++ over libcurl in order to send HTTP request?
Any suggestions/recommendations would be highly appreciated.
Thanks
The Google API Client Library is just a C++ wrapper around libcurl which is pure C library. I would use Casablanca REST SDK which is written in modern C++11, has no external dependencies and is cross platform.
Does Google API Client Library for C++ have support for HTTP Proxy? The use case examples for sending HTTP POST request at http://google.github.io/google-api-cpp-client/latest/guide/making_http_requests.html do not mention anything about HTTP Proxy Support. Does it have dependencies on external libraries like libcurl or libjingle for HTTP Proxy?
Thanks
I am new to services. I am sorry for my question being a little theoretical. On a site I was reading about SOAP, they said it works over internet.
Can we use SOAP based services in intranet environment ?
Can we use HTTP over intranet or it is just a internet protocol ?
Please guide.
You can use SOAP over any TCP network. This could be internet or intranet. SOAP is an interoperable protocol over HTTP. And HTTP works over TCP. So everywhere you have HTTP you can have SOAP. Basically SOAP is a protocol which allows for heterogeneous systems to communicate using an industry defined standards.
And note that SOAP is getting less attention lately compared to REST which is starting to gain lots of momentum.
SOAP is a service supported by a server/web service. You can even use SOAP to translate data between two services on the same server box that have no other form of API.