colly VS utls

SerpApi focuses on scraping search results. That's why we need extra help to scrape individual sites. We'll use GoColly package.

Interesting. Can you compare it to colly? [0]

Last time I looked it was the most popular choice for scraping in Go and I have some projects using it.

Is it similar? Does it have more/less features or is it more suited for a different use case? (Which one?)

[0] https://github.com/gocolly/colly

Sounds cool, but how is this different from Colly: https://github.com/gocolly/colly?

We could write some snippets mixing all these, but the best option in real life is to use a tool with it all, like Scrapy, pyspider, node-crawler (Node.js), or Colly (Go).

Unless you're specifically trying to do it using net/http, I recommend using colly. I've used it in a few scrappers and I love it!

In this blog, we will be covering the basics of web scraping in Go using the Fiber and Colly frameworks. Colly is an open-source web scraping framework written in Go. It provides a simple and flexible API for performing web scraping tasks, making it a popular choice among Go developers. Colly uses Go's concurrency features to efficiently handle multiple requests and extract data from websites. It offers a wide range of customization options, including the ability to set request headers, handle cookies, follow redirects, and more

github.com/gocolly/colly - popular and widely-used library for web scraping in Go. It provides a higher-level API than net/http and makes it easier to extract information from websites. It also provides features such as concurrency, automatic request retries, and support for cookies and sessions.

Does this offer any control at the TLS level? I have been looking for alternate TLS stacks for Go, and the only one I really found was uTLS:

https://github.com/refraction-networking/utls

Something that you'll run into for smarter anti-bot is that your JA3 tls signature will be checked. Easiest way to get around this is probably to use refraction-networking/utls. Especially true as go's tls signature is fairly unique.

Considering that the rocket league api isn't one of tracker.gg's listed apis, they probably enabled a lot of cloudflare'e antibot. If you really care to get around it, you can probably get fairly far with making sure you put the same headers as the chrome version you're trying to mimic. If that still doesn't work, then theres a chance that tracker.gg enabled ja3 fingerprint so you'd need to use a library like utls to fake your clienthello to look like chrome's.

do we have something like https://github.com/refraction-networking/utls but for rust?