Nostr Web Client

Yea i dont think i change fix it on my side, its because NIP-98 has the full URL and the host part doesnt match, if you redirect then your NIP-98 event will be rejected, you need to manually update the app to use the new API endpoint

Rod 4mo ago

I figured. Is there any possibility to continue to run the old endpoint until I can migrate?

I am AFK for a week.

Reply to this note

Please Login to reply.

Discussion

Rod 4mo ago

I am attempting to connect to the new API

"zap.stream/api/v1/account" With NIP-98 auth returns 200 with html body rather than expected API response

I also tried

"api.zap.stream/api/v1/account" returns 404

"api.zap.stream/api/nostr" returns 500

Do I have the right URL and auth?

Is this routing to the API correctly?

Kieran 4mo ago

The new URL is api-core.zap.stream, there is way to use redirects because nip98 has the full URL in the auth event

Kieran 4mo ago

No, the data was migrated to the new database, the old one is readonly

Kieran 4mo ago

I will have to disable host name validation by modifying the backend maybe, checking

Rod 4mo ago

I have tested and can connect with the new url.

If the old API is no op, and the new API has the same endpoints, then serving the new API from the old domain would solve my issue.

Is that possible?

Rod 4mo ago

i.e. new API replaces old at api.zap.atream domain. Nip-98 auth passes domain chexk. Then internal redirect from api/nostr to api/v1. Just thinking that may work. Not sure if possible

Kieran 4mo ago

Yea thats the way its setup but the backend expects URL to match new api url