1. Waiting for the whole page to load before allowing js to run is not necessary a good idea, and I see that is dealt with nfagerlund's pull request. 👍
2. Why is image proxy request returning that 504 error when the url does return the badge image in browser? (There is a 301 Moved response first, but Go should be able to follow redirects automatically so maybe it is something else. I don't know enough about Go or the setup to troubleshoot this.) I'm just wondering if this is a bug, too.
3. To avoid unnecessary image proxy requests, it would probably make sense to change the hardcoded FanFiction badge image url to point directly to the https protocol, as they do serve it in https.
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
malionette
no subject
Date: 2019-06-13 03:39 pm (UTC)I guess I see three things to look at.
1. Waiting for the whole page to load before allowing js to run is not necessary a good idea, and I see that is dealt with nfagerlund's pull request. 👍
2. Why is image proxy request returning that 504 error when the url does return the badge image in browser? (There is a 301 Moved response first, but Go should be able to follow redirects automatically so maybe it is something else. I don't know enough about Go or the setup to troubleshoot this.) I'm just wondering if this is a bug, too.
3. To avoid unnecessary image proxy requests, it would probably make sense to change the hardcoded FanFiction badge image url to point directly to the https protocol, as they do serve it in https.