Not sure why links to some domains throw a 202 like this… I’ve checked the onebox settings but can’t find anything wrong.
202 isn’t an error, it means “accepted”.
1 Like
Discourse seems to think it is though.
What I don’t understand is if the problem is on the Mudspike server or the linked server?
That’s rather unlikely. Can you elaborate on your observation and your expectation?
Background:
Every HTTP request has a return code:
- 2xx = success
- 3xx = redirected
- 4xx = client error
- 5xx = server error
Discourse apparently won’t render a preview for a page if the HTTP status code isn’t 200.
Whether that is Discourse’s fault or the remote server’s fault depends on an interpretation of the HTTP spec.
Maybe we should check if the IMDB link Wheels posted(1) returns a renderable HTML response with the 202 code, and if so, open a PR to Discourse to propose rendering a preview for 202-returning pages?
It’s almost like you all are speaking French.
My problem solving (stemming from aviation of course) is to turn it off..then turn it back on.
3 Likes
Ah I get it, it’s lazy loading of a dynamic web page.
Maybe a link like that works?
1 Like
First thing I tried man…
2 Likes
Well, the dialogue box says:
Sorry, we were unable to generate a preview for this web page, because the web server returned an error code of 202. Instead of a preview, only a link will appear in your post.
1 Like
Correct verbiage would be “returned a response code of 202”. As not every response code is an error.
So the web page is built to return 202 quickly, then lazy load the page asynchronously and send the content of the page later. Not something Discourse can help unless it also starts to do more work to load that page asynchronously.
A workaround could be to use a web proxy that does all that heavy lifting for Discourse.
But is it worth the effort? Personally I think links are fine.
2 Likes
I’m fine with links too. Just trying to wrap my head around the issue…
Codepen.io is somehow involved in the iframe creation. Make any sense to you?
Link expansion is done via something called a ‘Onebox’. I removed anything custom we had at the last upgrade, so if it doesn’t work then either the end site not providing info (like they block it or return empty etc) or it’s a discourse bug and you can log/look for it here - Latest Bug topics - Discourse Meta
4 Likes
I do love me some cake. But why is there one by my name?
4 Likes
I think it‘s your 10 year anniversary.
congratulations 
6 Likes
Congratulations on your first decade on Mudspike!
Cheers and on to the next!
3 Likes
You’ve been promoted to owner of Mudspike. I left the keys by the door. There are a few beers in the fridge. Keg is empty (of course). Thermostat is set on 68 (put a sweater on..you are really thin). Good luck.
(BLANK SPACE HERE WHERE I DID NOT PLACE THE APPROPRIATE GIF BECAUSE I KNOW YOU HATE THEM - I RESPECT THE NEW MANAGEMENT’S RULES)
6 Likes
Does this mean that the hired help can negotiate terms with the new owner..?
3 Likes
Take what they are paying you now and double it… 
4 Likes
As the new owner I have good news and some better news! (Though maybe not to all):
The good news: My hatred of gifs abides but has abated. I no longer go into epileptic fits when I see them. They are allowed! All the better to show off my new passion (and the better news)…
Bowfins! A fish. Also known as the “Mud Pike”. I’ll need to come up with a way to morph the site’s name to eliminate that pesky middle “s”. Meantime, all hail the MUDPIKE!
Only discussions and articles celebrating this wondrous fish will be allowed going forward. No planes, no politics. And certainly no helicopters! OK @Troll get ‘em all in line. We tolerate no whining about change at the new Mudpike.
9 Likes
So… Prescription meds cost money. I’m gonna need a raise.
7 Likes