I just saw this and became rather alarmed:
Any idea how this might happen?
This is sometimes the case when an (a?) user posts an image from an unsecure third party location.
That was my initial guess. Thanks so much for confirming though.
Wonder why this happens? Not updating the http to https initially and causing mixed content?
a user
Always use "a" when the word that follows sounds like it begins with a consonant and "an" when the word that follows sounds like it begins with a vowel.
Yup.
The mixed content error is gone now as the image has been mirrored on Discourses AWS cloud.
So... then USER doesn't sound like it begins with a vowel !
I so love English !
ye yusers yawned yesterday
Figured as much, "an user" didn't "sound" correct, even though the word user starts with a vowel. Didn't really realize it sounds like it starts with a consonant.
Ye King's Anglish ist wyrd.
These are scripts. schema, etc. (there's a bunch) @JuergenAuer pointed this out to me in a previous thread. Look at the source code.
Which are scripts? I'm not understanding. Do you mean the website architecture?
http://schema.org","@type":"QAPage","name":"Add an Hourly Duplicate Certificate Rate-Limit","mainEntity":{"@type":"Question","name":"Add an Hourly Duplicate Certificate Rate-Limit","text":"I cannot take credit for this suggestion, but I felt it to be so excellent that I just had to champion it.\n\n[image]<a href=\"https://community.letsencrypt.org/t/138258/5\">On another topic<\/a>\n\nI actually wonder if it'd be more helpful to add another rate limit, along the lines of no more than 2 duplicate certificates within a half hour (or maybe an hour)…","upvoteCount":3,"answerCount":0,"dateCreated":"2020-11-28T03:35:23.356Z","author":{"@type":"Person","name":"Jonathan Griffin"}}}</script>
etc, etc...
Is that the source code? Looks like JSON.
Yup. (I suppose I have to submit more text to allow the input.)
Interesting... Thanks for that.
By the way ... I am not getting the error.
It was momentary. I'm almost certain that Osiris hit it in one. Certainly worth making note of as a potential security hole though.
Wait ... I have to eat.
Enjoy your meal.
There already has been a thread about this.
Hmm, I think it was this one:
But I also remember a thread where the outcome was that something had been fixed.. Which is not the case for the thread above.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.