Can we bring back basic authorization credentials to the URL for APIs?
e.g. https://user:password@apiendpoint.com used to work but now there’s a type error
TypeError: Failed to execute ‘fetch’ on ‘Window’: Request cannot be constructed from a URL that includes credentials.
It was nice to be able to secure my end point if I wanted to run models locally for example. I understand there is the bearer key authorization but I still get sketched out opening up my computer to the internet.
Thanks for all you do!
Hey,
Unfortunately, Cursor has never supported local models, as our Cursor server’s have to be able to talk directly to the model providers.
Also, the bearer token model is also the only supported authorisation method, as this is the standard for most enterprise level LLM providers currently.
Yeah I understand. The workaround in the past is to use something like ngrok to set up a tunnel to localhost. I suppose the basic auth (username:password@url) features won’t come back then?
Any idea why they were removed?
I don’t believe this was an intended feature, and may have just been a built in feature of something we used inside Cursor. It’s possible we have removed or replaced that component, therefore inadvertently stopping this from working.
Thanks for the insight, Dan. Love using the product – hope it continues to improve.
Moses