asyncParseAsin fails to extract asin due to a 503 when the asin is already in the url

[alonseg]

test url: https://amzn.eu/d/hdFr7Ue
error: "https://www.amazon.co.uk/dp/B0CHN77WSN?ref_=cm_sw_r_apan_dp_HWW1YYCS0W4EYFMKFPEY&language=en-GB returned HTTP 503"

I'm running on cloud compute and amazon do not allow crawling from these IP, as you can see the "error" url contains the ASIN so it could have been extracted.

you can either test the regex on the url before throwing the error, or test the regex before even looking at the response code

[vaiden]

Works on my end - so I'm guessing it's blocked from your EC2 side.
Wanna share the full error response?

test url: https://amzn.eu/d/hdFr7Ue error: "https://www.amazon.co.uk/dp/B0CHN77WSN?ref_=cm_sw_r_apan_dp_HWW1YYCS0W4EYFMKFPEY&language=en-GB returned HTTP 503"

I'm running on cloud compute and amazon do not allow crawling from these IP, as you can see the "error" url contains the ASIN so it could have been extracted.

you can either test the regex on the url before throwing the error, or test the regex before even looking at the response code

[alonseg]

thanks for the reply, I'm running it on a DigitalOcean dropplet, and indeed when trying to acess amazon urls from it I get 503.

but my issue here is that the shortened url gets a proper redirect as expected, and when trying to access the full url with expected 200 status code, I get 503 and the amazon-asin package throws an error.

the 503 is returned when it already holds the full url with the asin in it, so it could have parsed the asin out of it.

I will try to create a PR that handles it and would appreciate your review and comments

[alonseg]

I've now realized that the issue is in [resolve-redirects-efficient](https://github.com/vaiden/resolve-redirects-efficient), I'll create the PR there

[alonseg]

@vaiden when you get the chance, please take a look at the PR I've created