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'                               

When using the url http://docs.python-requests.org/en/latest/, it redirects to https://2.python-requests.org//en/latest/ (notice the extra / before en). This causes a HTTP 404.

Expected Result

The redirect should be to https://2.python-requests.org/en/latest/

Actual Result

HTTP 404

Reproduction Steps

Try to visit the latest en documentation for requests using the

(Feature request out of https://caddy.community/t/use-placeholders-in-templates/7697)

I would like to see the ability of using placeholders like {http.error.status_code} in templates. This would allow us, for example, to create a single custom error page in nginx style. For now we have to create a page for every status code we would like to support (maybe using respond with include and ar

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

Is your feature request related to a problem? Please describe.
The {{< highlight none >}} :~q:foo:bar {{< / highlight >}} blocks don't work on GitHub. It's confusing and makes the code examples almost useless on GitHub itself. And also in your code editor if you have Markdown syntax highlighting with embedded highlighting for nested code.

Describe the solution you'd like

It'd be ne

I want to use the SFTP protocol to create folders on the remote SFTP server, without specifying the curl option. The option created on the FTP protocol is "CURLOPT_FTP_CREATE_MISSING_DIRS".
Do you have any corresponding SFTP options?
Thanks for any help.

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

RFC 7231 Section 6.5.5

States that

The origin server MUST generate an
Allow header field in a 405 response containing a list of the target
resource's currently supported methods.

Which is clearly not implemented right now
https://github.com/gorilla/mux/blob/75dcda0896e109a2a22c9315bca3bb21b87b2ba5/mux.go#L601-L603

Sugg

The documentation does not make it clear whether
paths of the form:

/prefix:foo

are allowed. These are currently supported by httprouter,
but don't seem quite in the spirit of its simple specification
(you can't have statically defined suffixes for a path element,
so why should you be allowed a statically defined prefix?)

This form:

/prefix*foo

is similarly not specified but i

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

Nock has two APIs:

1. The part that faces the developer writing tests – the public interface
2. The part that faces the HTTP client library –  the mock surface, for lack of a better name

The mock surface is implemented in a few places:

• A couple functions in common.js which are the mock http(s).get and http(s).request calls
• request_overrider.js, the mock response
• `intercept.

A small pet peeve of mine is that the --ssl option enables TLS, not SSL. I accept that the tech world uses these related but different terms interchangeably, but I'd rather be more correct by default.

To do:

1. Replace the existing --ssl option with --tls.
   a. Note that this enables "TLS/SSL" in the documentation so it doesn't confuse people.
   b. The short option -S could stay th

I'm submitting a ...

• bug report
• [ X] feature request
• question

PostGraphile version: 4.4.4

postgraphile should honor variables in query string as defined in https://github.com/graphql/express-graphql#http-usage when the query is provided as post body.

with the following exampl

F1 simply prints "11~" in whatever field I have selected.

Debian GNU/Linux 9.5

I always feel bad about my first contact with developers being a bug report or complaint; so I wanted you to know how cool I think this. Thanks for your efforts!

I'm upgrading a build environment from python 2 to python 3 and noticed that endpoints with seeded random numbers are not returning the same values. It seems to be related to usage of randint:
https://github.com/postmanlabs/httpbin/blob/f8ec666b4d1b654e4ff6aedd356f510dcac09f83/httpbin/core.py#L1448

It seems like randint is not seed safe and it looks like only random() is: https://bugs.python.o

Currently, we ask contributors to strive for consistency with existing code, but it would be helpful to clarify the following regarding docstrings:

• Docstrings should begin with a short (~70 characters or less) summary line that ends in a period.
• The summary line should begin immediately after the opening quotes (do not add a line break before the summary line)
• The summary line should de

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

It would be great to add regex capabilities to redirects like so:

redirects: {
  "/folder/:slug(regexhere)": {
    "location": "https

I think the docs are a bit thin. Would be nice with a tutorial on how to use the feature that takes advantage of all the options.

And sindresorhus/got#833 (comment)

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

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

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