-
Notifications
You must be signed in to change notification settings - Fork 19
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
Upload media returns wrong processing_url #34
Comments
Hello, can you send me the complete message returned by the server? "RES -> 400 Bad request - Auth header (NIP98) event endpoint is not valid", eventEndpoint, "<>", ServerEndpoint, "|", getClientIp(req)); The ServerEndpoint that the server expects should also appear in the response. Thank you! |
Hey, |
Are you using the endpoint https://cdn.nostrcheck.me/{id} with the GET method to check the file status? Or are you instead using https://nostrcheck.me/api/v2/{id}? In theory, if you use the endpoint that returns processing_url and construct a NIP98 header following the specifications, it should work for you. Both endpoints lead to the same site, but the 'u' tag in the NIP98 header must match. On my end, I’ll review the documentation; there’s probably an issue there as well. |
I use the https://cdn.nostrcheck.me/{id} which is returned as processing_url and then I construct the NIP98 header with this url in 'u' tag. And send the GET request to this url and receives the error. On the other hand if I modify the url like this https://nostrcheck.me/api/v2/media/$id, construct NIP98 and send the request, it works. |
Temporary solution applied, waiting until it can be resolved definitively. |
Describe the bug
When I upload a larger image via Media upload, the upload request returns a processing_url. However, the processing_url is in a different format than what is described in the documentation. In the documentation, the format is "https://nostrcheck.me.com/api/v2/media/3225," but for me, it appears as "https://nostrcheck.me.com/3225." When I try to check the status of the image, the response is: "Auth header (NIP98) event endpoint is not valid: https://cdn.nostrcheck.me/141473." However, when I format the URL according to the documentation, it works as expected.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The processing_url should be returned in the format specified in the documentation.
Screenshots
![Screenshot 2024-12-15 at 17 39 09](https://private-user-images.githubusercontent.com/56815552/395879012-fefceb2c-6c3c-4195-a9dc-cd47f66c84ff.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzM5NzksIm5iZiI6MTczOTI3MzY3OSwicGF0aCI6Ii81NjgxNTU1Mi8zOTU4NzkwMTItZmVmY2ViMmMtNmMzYy00MTk1LWE5ZGMtY2Q0N2Y2NmM4NGZmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDExMzQzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTlhMzNiMWZhNmM0NjVlNjIyZGIxZTI5MDQ3NDVkMWVkOGE3YmNkMjRmM2FiYWRhOTA5MWRmOGQ0NmFlNjRiMzAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.RIJLjbH0d5ftv0I5Nsm4DNfy65cXT1SY_oLrNjOwUDg)
![Screenshot 2024-12-15 at 17 56 49](https://private-user-images.githubusercontent.com/56815552/395879026-ccebad5f-d87c-40c3-bb36-72aee8fbe3c1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzM5NzksIm5iZiI6MTczOTI3MzY3OSwicGF0aCI6Ii81NjgxNTU1Mi8zOTU4NzkwMjYtY2NlYmFkNWYtZDg3Yy00MGMzLWJiMzYtNzJhZWU4ZmJlM2MxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDExMzQzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTg0Njk5M2YzODNiNGMwNzYyY2I1ZDE0NzMzNTVmZTAwZGU2NWFkMjAxZTQzODYzODU1MmZhNzdiMmYwNGY5NDEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.-tRnsfo6vxlhjIs_Eh948Kuh72yIQxEWU9n9WSp2nhc)
Desktop (please complete the following information):
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: