gocolly / site Goto Github PK

Visiting https://go-colly.org/ shows a different website (omnom) instead of colly's.

There must be an issue on the nginx configuration, where the backend for port :443 seems to be redirecting traffic to another website, instead of colly's documentation.

As seen on this issue: gocolly/colly#694

http://go-colly.org/docs/introduction/start/ The OnResponseHeaders function is a recent change added and it is called before OnResponse. The list should be updated to reflect this

I was searching on the source code why many links get static files using http:// protocol. That produces a mixed-content error. This is why the web is broken.

If you go to get started page. You will see that the CSS is not loading. If you open the network inspector, you will see an error while loading CSS saying mixed-content.

Checking the source code, I found that the file inside themes/colly/layouts/_default/baseof.html you will that the link tags that import static files uses absURL. This function as you can see in hugo docs takes the baseURL and the provided path and generates the full URL of the asset. This error may happen to the rest of the page.

Try to change the baseURL link setting, the https protocol. Also, review that more links use the correct protocol. I hope this could help.

Can I use the theme (especially the CSS ) for another repo?

The .css and .js files are being loaded via http but the site is on https, so chrome is blocking those assets from loading

Now that gocolly/colly#82 has been merged we should probably update the documentation to match.

@asciimoo I'm happy to do it if you don't want to :)

Pages that should be updated: (Might not be a complete list)

• http://go-colly.org/docs/best_practices/debugging/
• http://go-colly.org/docs/best_practices/multi_collector/
• http://go-colly.org/docs/best_practices/crawling/
• http://go-colly.org/docs/examples/basic/
• http://go-colly.org/docs/examples/max_depth/
• http://go-colly.org/docs/examples/multipart/
• http://go-colly.org/docs/examples/parallel/
• http://go-colly.org/docs/examples/proxy_switcher/
• http://go-colly.org/docs/examples/rate_limit/
• http://go-colly.org/docs/examples/url_filter/
• http://go-colly.org/docs/examples/coursera_courses/
• http://go-colly.org/docs/examples/instagram/
• http://go-colly.org/docs/examples/openedx_courses/
• http://go-colly.org/docs/examples/xkcd_store/

It looks like either could be correct, but one spelling is used in the source and another on the site.

I assume the code would be the one to keep, and the site the one to change.

Hello Sir ,
I'm a Chinese native-speaking developer, and I love Colly very much.
I'd like to contribute a Chinese version of Colly documentation for http://go-colly.org/.
What can I do?
Thank you!

Please force all request to https