Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow null values for username and password - libcurl problems #111

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

0xC9C3
Copy link

@0xC9C3 0xC9C3 commented Sep 6, 2023

Currently no null values are allowed for username and password.

This leads to potentially undesired behavior when guzzle/psr7 is used as Uri builder.

See this line https://github.com/guzzle/psr7/blob/2.6/src/Uri.php#L438

Currently only strings are allowed which means any url without any auth information will be built like this:

https://:@DOMAIN.TLD/...

This is seemingly not an issue for older curl versions.

We had the case where we upgraded from libcurl 7.79.1 to 8.0.1 and our application stopped working. This is because newer curl versions respect empty Http Basic auth and still set the proper header values. In our case this prevented the communication to AWS OpenSearch, since no authentication was expected.

If like in our case no authentication should be used, valid yaml null values like null and ~ could be used to type safe set those to null.

Let me know if you need changes or more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant