In = syntax,

• double quotes (")
• back slashes (\)
• non-ascii characters

are escaped in json.dumps:

$ http -v httpbin.org/post                                      \
    dquote='\"'                                                 \
    multi-line='line 1\nline 2'                               

It could help potential new contributors if the "How to Contribute" section included the content or a link to the "Good Bug Reports" section of the contributing.md and a link to some simple example tests in step 4

1. What would you like to have changed?

Right now caddy2 has two config adapters: Caddyfile and JSON.
I have to admit, that I am not a big fan of json, because it's not possible to insert comments and it's difficult to write manual.

JSON is a format that should be used only from one comput

This is more of a question, as I couldn't find it in the documentation. Does aria2 do any checks when downloading a file from multiple sources to ensure all of them are actually referencing the same file? Some basic checks might be based on comparing: 1) file size, 2) date (might not be consistent or even available), 3) first and last few bytes, 4) small chunk overlap, and compare the small ove

Problem Description

In https://github.com/mitmproxy/mitmproxy/blame/master/docs/src/content/tute-clientreplay.md#L35, Toggle Proxy is linked, but it no longer exists.

Steps to reproduce the behavior:

1. GOTO https://docs.mitmproxy.org/stable/tute-clientreplay/
2. GOTO https://addons.mozilla.org/en-us/firefox/addon/toggle-proxy-51740/
3. SEE Oops! We can’t find that page

Sy

I did this

Using curl with alt-svc support compiled in:

$ curl --alt-s

Documentation overhaul

Vegeta's documentation today is OK, but it can be substantially improved. This issue is meant to track ideas and needs for better documentation.

examples/ directory

All common (or not so common) recipes and examples ought to be captured in an appropriately named file in the examples/ directory, be they CLI or library related.

The README should be reduc

I can't find any other explanation or formulas for results like median, average, min/max, req/sec in documentation, readme or web page. On the documentation page I tried basic scenario to search result/s and get no relevant page.

I found this question on stackoverflow, so I'm not only one who didn't understand it
https://stackoverflow.com/questions/39665250/locust-result-summary-how-to-underst

Hello,
My project begin to growth and i'm asking myself about documentation generator, do you know if they are existing generator of api documentation ( with annotation maybe ? ) or if it's planned to integreate API generator by routes or by annotation ?

Best regards,
Henri

At the moment, "/param1a%2fparam1b/tail" matches route "head/:param1/:param2/tail" instead of ":param1/tail". There's no way we can have a '/' in a URL param.

If you're using proxies with requests-html and rendering JS sites is all good. Once you render a website pyppeteer don't know about this proxies and will expose your IP. This is an undesired behavior when scraping with proxies.

The idea is that whenever someone passes in proxies to the session object or any method call, make pyppeteer also use these proxies. #265

Long story short

Regression of #1188

Expected behaviour

Tests pass on armv7l

Actual behaviour

Test run fails at test_cookiejar.py:383: OverflowError

Steps to reproduce

Run tests

Your environment

linux 4.19
nixos 20.03
arm v7l
python 3.7
aiohttp client-3.6.2

Log

        ts_before = datetime.datetime(
            1975, 1, 1, tzinfo=datetim

What is the expected behavior?

Expected that the following would block requests to https://domain.com

nock('https://domain.com');

What is the actual behavior?
It doesn't! It looks like the scope will only intercept the request once a complete interception (scope, request, reply) is in place.

Possible solution
Perhaps update the docs to clarify this? I don't real

I cannt found documention of the show_env parameter from https://httpbin.org/.

despite the default behavior of httpbin is very odd, it hides many HTTP headers which are very important to some user, like me, a sysadmin, this behavior and the method to flip it, needs documentation.

Correct the terminology used in code and documentation so that it is consistent with HTTPie and web standards. Examples:

• body parameter -> data field
• operator -> separator

What would be the minimal IAM Policy for deploying, I know the policy on the website, but that has also access to EC2 and is quite broad. For example I would not need to control a domain from there.

Like it would be a role that you could put on Travis-CI and not worry about them deleting your EC2 instances.

I tried deleting everything other than Lambda, API Gateway and S3, but then I began

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

The default value of falcon.RequestOptions.auto_parse_qs_csv was changed to False in v2.0 and handled in falconry/falcon#842 and falconry/falcon#1318.

The FAQ item https://falcon.readthedocs.io/en/stable/user/faq.html#how-do-i-consume-a-query-string-that-has-a-json-value assumes the old default value and needs an update.

The Go documentation states the following on http.Request.RemoteAddr:

The HTTP server in this package sets RemoteAddr to an "IP:port" address before invoking a handler.

Therefore, you could expect that a code like this is correct:

package main

import (
	"fmt"
	"net"
	"net/http"

	"github.com/go-chi/chi"
	"github.com/go-chi/chi/middleware"
)

func main() {
	r

We never have enough tests. There are just so many edge-cases in HTTP and networking that the more the merrier.

It could be useful to look at other popular request libraries and take see if they have tests we are missing:

• request
• axios
• node-fetch
• [ky](https://git