| Textstyles |
|---|
| Size | 16px |
|---|
| Color | rgb(236,0,140) |
|---|
|
WORK IN PROGRESS | Services are in active development and are subject to change.
|
Charity Engine's Proxy Service is used just like a standard HTTP proxy. It is accessed by configuring the system or application proxy settings to route requests through it:
| Code Block |
|---|
|
Host: charityengine.services
Port: 20000 |
Once requests are fulfilled by Charity Engine computers, the responses are returned as though the request was made directly. Try a simple example using curl:
| Code Block |
|---|
|
curl -v -k -x charityengine.services:20000 -A "Mozilla/5.0 ..." --proxy-user "(authenticator):" "https://www.example.com"
|
This will send an HTTPS request to example.com through the Charity Engine Proxy using a Mozilla/5.0 user-agent. When the request is complete, it will return the contents of the page at the given URL.
| Info |
|---|
Use an appropriate user-agent string and replace (authenticator) with a valid Charity Engine authenticator. If you still need one, contact us to get started! |
| Textstyles |
|---|
|
Better Performance
|
It is recommended that requests be submitted to the proxy in parallel. A single slow request could take 20 seconds, but in the meantime, hundreds of other requests could be sent, processed, and returned in parallel.
| Textstyles |
|---|
|
Advanced Options |
Additional HTTP headers can be sent to use proxy service configuration options. For example, add --header "X-Proxy-Country: US" (including quotes) to only use nodes from the United States. For details on this and more capabilities, examples, and troubleshooting, see the Distributed Proxy Service documentation.