You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I found a bug in the queue logic. You build the url like this ${APP_SERVICE_URL}/${APP_SERVICE_QUEUE_ENDPOINT}?secret=${taskSecret}
while the APP_SERVICE_QUEUE_ENDPOINT is /mndy-queue and the user may add APP_SERVICE_URL with / at the end.
This causes the endpoint to be ///mndy-queue instead of /mndy-queue.
The best solution in my opinion will be to generate the url like this new URL(APP_SERVICE_URL, APP_SERVICE_QUEUE_ENDPOINT)
I tried to develop that but failed building the developer container...
Thanks,
Ram
The text was updated successfully, but these errors were encountered:
Hey,
I found a bug in the queue logic. You build the url like this
${APP_SERVICE_URL}/${APP_SERVICE_QUEUE_ENDPOINT}?secret=${taskSecret}
while the APP_SERVICE_QUEUE_ENDPOINT is /mndy-queue and the user may add APP_SERVICE_URL with / at the end.
This causes the endpoint to be ///mndy-queue instead of /mndy-queue.
The best solution in my opinion will be to generate the url like this
new URL(APP_SERVICE_URL, APP_SERVICE_QUEUE_ENDPOINT)
I tried to develop that but failed building the developer container...
Thanks,
Ram
The text was updated successfully, but these errors were encountered: