Get-S3Bucket : Invalid URI: The format of the URI could not be determined. about aws-sdk-net HOT 15 OPEN

Could this be related to #3198? We added support for http_proxy a while ago, but no_proxy was missing (this was fixed in version 4.1.525 of the AWSPowershell modules).

from aws-sdk-net.

Hi Daniel,

Yes, we have checked this issue yesterday, but even with 4.1.525, we are getting this "Invalid URI" error and from that message it's hard to decide, where the issue is coming from exactly. In the "Current Behavior" section I have specified the versions being tried and the respective error messages.

from aws-sdk-net.

I'm not sure if you can share it, but what does your no_proxy look like? I know we're not ignoring it anymore, but from the PR:

The full implementation of no_proxy would involve DNS resolution to IP address and CIDR matching. That is a much larger scope to integrate into the SDK and for the SDK's use cases unlikely to be needed. This implementation does host name matching with wildcard support matching the Java and Kotlin SDK's implementation.

from aws-sdk-net.

I can't share the exact details, but I am using an example.
Target endpoint: https://example.target.company.com
Env vars in the script:
$proxy = "http://proxy.company.com:8080"
$noProxy = "127.0.0.1;localhost;example.target.company.com"
$noProxyComma = "127.0.0.1,localhost,example.target.company.com"

We have tried unsetting the $proxy variable as well, but didn't change the outcome.

from aws-sdk-net.

@KristofKuli What is the no_proxy being set to. The value of $noProxy or $noProxyComma?

from aws-sdk-net.

$noProxyComma

from aws-sdk-net.

Hi,
is there any update on this?

from aws-sdk-net.

Please enable logging to see if it helps in identifying the issue. PowerShell logging can be enabled with below commands.

    Add-AWSLoggingListener -Name "AWS Logs" -LogFilePath "C:\Logs\ps-logs.txt" # or any path
    Set-AWSResponseLogging Always
    Enable-AWSMetricsLogging

from aws-sdk-net.