On Thu, 8 Jun 2023, Chamberlin, David wrote:
For the test we are looking to adding another test case in tests/data - does
that seem right?
Yes
I don't see anything that explicitly tests the 8K limit - or might that be
somewhere else?
No, we might have not gotten around to do that. But we
On Thu, Jun 08, 2023 at 05:40:04PM +0200, Daniel Stenberg via curl-library
wrote:
> Just a few days ago, Dan Fandrich merged the necessary commits into master
> that now lets us try out running the curl tests in parallel as compared to
> the old serial way.
It's been a long road of refactoring
Hi friends,
Just a few days ago, Dan Fandrich merged the necessary commits into master
that now lets us try out running the curl tests in parallel as compared to the
old serial way.
This can make a test round complete more than twenty times faster than before.
If your machine is up to it.
We'll hold off on the cookie length limit for now, then and wait to see what
happens.
We are planning to submit a pull request with a test and the fix for the length
calculation issue.
The impact is that the real limit for cookie size may actually end up being
somewhat less than 8K.
For the
On Thu, 8 Jun 2023, Daniel Stenberg via curl-library wrote:
I'll fix and make sure we add test cases for this. Thanks for reporting!
PR: https://github.com/curl/curl/pull/11272
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support,
On Thu, 8 Jun 2023, Timothe Litt via curl-library wrote:
If a path is set in the URL without a leading slash, a slash will be
inserted automatically when this URL is read from the handle.
While you're at it, doc should be "trailing slash". "leading" - the
beginning (left). "trailing" - the
On 08-Jun-23 03:18, Daniel Stenberg via curl-library wrote:
On Thu, 8 Jun 2023, Pedro Henrique via curl-library wrote:
but the code below results in 400 Bad Request due to the lack of the
forward slash.
So is it a bug or not?
I can confirm that this is a bug and that it still exists in
On Thu, 8 Jun 2023, Pedro Henrique via curl-library wrote:
but the code below results in 400 Bad Request due to the lack of the forward
slash.
So is it a bug or not?
I can confirm that this is a bug and that it still exists in current code.
If you set the path like that and extract the full
