Loading
Commits on Source 37
-
Tiago authored
-
Tiago authored
-
Tiago authored
localstack wants me to create an account...
-
Tiago authored
its downtime has been a bit of a drag...
-
Tiago authored
-
Tiago authored
this allows running regression tests again in a dind container system, which doesn't expose it to issues with nghttp2 again.
-
Tiago authored
also, synching access to the token inside a session, as it may be used across threads
-
Tiago authored
-
Tiago authored
can happen in rate-limiter plugin scenarios if the date is in the past
-
Tiago authored
-
Tiago authored
before, a comparison like what is done to compare connections was done, but this is not correct, as small differences, such as different origin or path, should not matter, i.e. the resolver should do them the same, as long as the resolver-related options (resolver class, cache, options, etc) are the same). the comparison of connections options which may match is also decoupled from the main options equality operation.
-
Tiago authored
so it can be reused
-
Tiago authored
this has an adverse effect in multi-host multi-request situations, where in the context of a web server, retries or shutdown may be delayed because of premature context switching this is anyway a problem of the ruby thread scheduler which needs to be smarter, and would only benefit situations where the pool max connections is set and is way lower than the number of threads
-
Tiago authored
-
Tiago authored
can be tcp low level packet ACK stuff, can be openssl...
-
Tiago authored
in a scenario where multiple requests were being sent to a connection which needs ping-for-liveness, several pings were being sent, even if only one of them would get a response; this fix ensures that a single ping is sent for the full batch.
-
Tiago authored
now that we have this, we don't need to set the state in a dirty manner in the pre-check.
-
Tiago authored
spare a potentially needless round trip to the selector by doing so.
-
Tiago authored
this is not a real fix, but it should hopefully help pinpoint the state of the connection at the time while not disrupting daily business
-
Tiago authored
-
Tiago authored
-
Tiago authored
also, improve sig check by using local vars in dispatch flow.
-
Tiago authored
`parser.handle_error` may, in some cases, disconnect the connection (by calling `#reset`), which may make it available to another thread, which may have already fiddled with the ivars. to guard against it, before calling the method, the connection pending list is copied into a local var and flushed.
-
Tiago authored
this fixes an issue when raising RequestTimeoutError, as this timeout may not be raised before the request traverses multiple connections (via the persistent or follow redirects plugin), while the original callback was being raised in the first connection the request was sent to. This fixes it by keeping a reference to the current connection the request is currently in; this reference is removed when the request finishes, i.e. when the error response is assigned, or the response finishes.
-
Tiago authored
-
Tiago authored
-
Tiago authored
-
Tiago authored
the main purpose of the test is to verify that the connection does not go down with protocol error, as there are cases where the server won't send any more chunks back, despite the client having sent data chunks that were ignored prior to reconnection
-
Tiago authored
skip expect tests relying on delayed body delivery, as httpbin sometimes closes the socket after intermediate response
-
Tiago authored
no real point
-
Tiago authored
that jruby-openssl breaks the test server impl
-
Tiago authored
this created a situation where the requests would be reenqueued when the connection would be reused after closed (persistent), which would cause these requests to be reenqueued later when transitioning the connection to idle to ensure this requests are drained from the parser as the error is bubbled up to the connection
-
Tiago authored
which the connection may have reset to 1 based on prior knowledge also, and based on the disable pipelining flow, when resetting requests, transition them back to :idle before marking them as pending
-
Tiago authored
this should mean that a connection reset back to idle as part of error handling, such as in the case of disabling pipelining for HTTP/1.1, so this skip is to avoid double-resetting
-
HoneyryderChuck authored
auth: only generate token on retry once for a given batch of requests Closes #377 See merge request !443
-
Tiago authored