Running KM locally fails connecting via localhost.

[SophisticatedConsulting]

Context / Scenario

I am trying to upload documents stored in local Azure Storage (via Aspire/Docker). I retrieve a temporary url for this and upload the document to memory kernel via ImportWebPageAsync()

The upload fails as local addresses are not allowed (even in a dev environment).

What happened?

There is specific 'hard code' that breaks local testing in both MemoryService and MemoryWebClient:

ImportWebPageAsync(...)
...
            Verify.ValidateUrl(uri.AbsoluteUri, requireHttps: false, _allowReservedIp: false_, allowQuery: true);
...

I cannot see anyway to override this without hacking the code.

Importance

I cannot use Kernel Memory

Platform, Language, Versions

Current version (code)

Relevant log output

[dluc]

The logic is intentional, to avoid malicious calls to local services. If you need to, you can work around it by aliasing your local IP in your local DNS, e.g. entering this line in your hosts file:

# Custom alias for Kernel Memory (use any name you like)
127.0.0.1   myhost

and use http://myhost/path instead of http://localhost/path

[SophisticatedConsulting]

Hi @dluc.
Thanks for your prompt response and suggestion.
Yes... I was able to access the service locally using a local dns setting (and without hacking the code!)... however, I was not able to get this to work with a local azure storage Docker service (created through aspire) and I cannot see a workaround for this.
When I create a temporary link to an Azure Storage document to feed to Memory Kernel for chunking, it is created with a localhost url. I cannot change the url (replace localhost with the new domain created in hosts), as this invalidates the access (I guess the access token is created for a specific url).
The current situation is that I cannot run both locally.
Do you have any suggestions?
Much appreciated.