Info Provider LCSC - LCSC returns 403 on v2.0.2

[h0lad]

Describe the bug

LCSC component search doesn't seem to work it always returns an 403.

If I open one of these URLs in a browser I get this

I've tested this from several IPs (Dialup and Server). Also with a manual "wget" and faked Browser headers.

To Reproduce

1. Activate LCSC as info provider
2. Search for a component

Server Side

• Part-DB Version: v2.0.2
• PHP Version: PHP 8.2
• Database Server: SQLite

[teriot-iot]

I like Part-DB a lot and use it on regular basis. It improved my workflow a lot.
Big thumbs-up & thanks to all contributors!

Unfortunately, we have the same issue with LCSC.
I had a brief look yesterday and it seems that most (if not all) information we need are embedded in the HTML file as JSON object.

an example URL is: https://www.lcsc.com/product-detail/C2333.html?s_z=n_C2333

When looking into the source of the page I can see 2 JSON elements like this:

<script data-n-head="ssr" type="application/ld+json">{"@context":"http://schema.org","@type":"ImageObject","name":"BOOMELE(Boom Precision Elec) 2.54-2*40P","description":"250V 3A Through Hole Pin Header 80P -25℃~+85℃ 2.54mm 2 Black 2x40P 2.54mm Through Hole,P=2.54mm Pin Headers ROHS","contentUrl":"https://assets.lcsc.com/images/lcsc/900x900/20221227_BOOMELE-Boom-Precision-Elec-2-54-2-40P_C2333_front.jpg","thumbnail":"https://assets.lcsc.com/images/lcsc/900x900/20221227_BOOMELE-Boom-Precision-Elec-2-54-2-40P_C2333_front.jpg"}</script>
<script data-n-head="ssr" type="application/ld+json">{"@context":"http://schema.org","@type":"Product","name":"BOOMELE(Boom Precision Elec) 2.54-2*40P","sku":"C2333","mpn":"2.54-2*40P","brand":"BOOMELE(Boom Precision Elec)","description":"250V 3A Through Hole Pin Header 80P -25℃~+85℃ 2.54mm 2 Black 2x40P 2.54mm Through Hole,P=2.54mm Pin Headers ROHS","image":"https://assets.lcsc.com/images/lcsc/900x900/20221227_BOOMELE-Boom-Precision-Elec-2-54-2-40P_C2333_front.jpg","category":"Connectors/Pin Headers","offers":{"@type":"Offer","url":"https://www.lcsc.com/product-detail/C2333.html?s_z=n_C2333","priceCurrency":"USD","price":"0.1208","itemCondition":"http://schema.org/NewCondition","availability":"http://schema.org/InStock","inventoryLevel":15795,"seller":{"@type":"Organization","name":"LCSC Electronics"},"description":""}}</script>

that might be a way how to work around the issue.
However, my PHP skills are not so good and for me it would take a lot of time to get a somehow working solution.

The first idea was to implement a custom Provider as a short-term solution.

Another idea was to have a further look into the LCSC API maybe this would be the better way forward (e.g. like with Mouser).

But as said, my skills are very limited in PHP and for me this would be a lot of effort.

[DrNorfolk]

I confirm. I have exactly the same problem for about 2 days - Error 403. I tried with different IP. I like this provider, I would like to use it in the future

[jbtronics]

It is also possible that to retrieve some info about a part, via an API of EasyEDA: https://easyeda.com/api/products/C145305/components?version=6.4.19.5

[jbtronics]

I actually found another search API (basically the same as before, but just with a v2 in the URL, and it wants POST instead of GET requests). With the latest commits, the LCSC provider now seems to work again.

Also LCSC seems to have changed something on their servers again, so that the detail retrieval API endpoint is working again. Im pretty sure that i got error messages from it just yesterday, and today it is working fine again...

[DrNorfolk]

Great! With the last commit everything works again. I just manually corrected the LCSCProvider.php file (replaced GET with POST, added v2 and replaced "query" with "json"). Everything worked - great!
I just updated the docker container, but apparently the changes haven't been made to it yet.

[h0lad]

Thanks for the fast fix! Now I finally can open the latest LCSC component delivery and add them to PartsDB :-)