HTTP
HTTP (Hypertext Transfer Protocol) is a request and response protocol used to send a request to a server and receive a response back in the form of a file. HTTP is the basis of data communication for the web. HTTPS is an evolution in HTTP, where the “S” stands for secure socket layer allowing communication in HTTP to be more secure.
Here are 6,519 public repositories matching this topic...
Summary.
Sphinx documentation 'make html' throws warning about https://2.python-requests.org/en/master/objects.inv
Expected Result
Sphinx make can pull the objects.inv without problems
Actual Result
(phsa_venv) phsa@lvmsocq01:~/p_soc_auto/docs$ make html
Running Sphinx v2.1.2
loading pickled environment... done
loading intersphinx inventory from https://2.python-reques
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
After installing profile and activating it, Safari still shows websites as "not trusted" and apps show "network error"
Steps to reproduce the behavior:
- Configure wifi to use mitmproxy
- Install and activate profile from mitm.it
- Navigate anywhere in Safari
refs mitmproxy/mitmproxy#3649 (added EKU) and #3647
System Inf
smtp-mime.c example
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
Since you can specify the target host on the Locust class I don't see a need to having to specify it again with an environment variable. Could this restriction be removed, or am I missing something?
You should never need GBs of backpressure but performance is nevertheless horrible in these cases.
substr for every sent chunk is a very bad strategy and should prefer keeping large buffers intact instead.
Only substr smaller backpressure, keep large buffers as is.
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
-
Updated
Feb 13, 2020 - Shell
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
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
Actual:
$ curl -vvv https://httpbin.org/absolute-redirect/2 |& grep Location
< Location: http://httpbin.org/absolute-redirect/1
Expected:
$ curl -vvv https://httpbin.org/absolute-redirect/2 |& grep Location
< Location: https://httpbin.org/absolute-redirect/1
=> I would expect that the used protocol is conserved in the absolute-redirect feature.
-
Updated
Feb 13, 2020 - JavaScript
-
Updated
Feb 13, 2020 - Go
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
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, --verboseflag. - Are you an Up Pro subscriber?
Description
Currently the TLS version defaults to 1.0. I have to manually upgrade it to 1.2. So it would be nice if it could be specifed in the custom
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
Based on a question from our community (by @amarynets), where one is wondering whether setting resp.complete = True in process_response will stop any remaining process_response methods.
The docs state clearly
However, any
process_responsemiddleware methods will still be called.
The context is, however, setting resp.complete from process_request & process_resource, not `proc
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
In
=syntax,")\)are escaped in
json.dumps:$ http -v httpbin.org/post \ dquote='\"' \ multi-line='line 1\nline 2'