XF 1.4 Unknown proxy mode errors

Stuart Wright

Well-known member
Google webmaster tools has alerted me to a bunch of 500 errors. E.g.
Code:
https://www.avforums.com/proxy.php?image%3Dhttp%253A%252F%252Fi679.photobucket.com%252Falbums%252Fvv155%252FSnakePliskin2009%252FArnie_zpsf31b0d13.jpg%26hash%3De18819584ecb1587c9930eeeb48dd9d8
which is in this post:
https://www.avforums.com/threads/terminator-genisys-26-june-2015.1055144/page-12#post-20484119

I *think* that's a pasted URL from photobucket?
Anyhow, trying to go to that URL above gets an Unknown proxy mode error.
If Google tells me about it, maybe it's a big deal?
 
That's not actually a valid proxy URL, the components are double encoded. Thus, an error would be expected. I couldn't say exactly how it happened, but I would guess that the actual image URL is that value (as local images aren't proxied) so it was invalid when it was provided.
 
That's not actually a valid proxy URL, the components are double encoded. Thus, an error would be expected. I couldn't say exactly how it happened, but I would guess that the actual image URL is that value (as local images aren't proxied) so it was invalid when it was provided.
I edit the thread and swap to the code view and it's this:
Code:
Arnold appears to have gotten back in shape again too.

Quite impressed by how he looks - nice work Arnie.

This has taken at least a decade off his appearance IMO ....

[URL='http://s679.photobucket.com/user/SnakePliskin2009/media/ARnold-teaser_zps74843e05.jpg.html'][IMG]http://i679.photobucket.com/albums/vv155/SnakePliskin2009/ARnold-teaser_zps74843e05.jpg[/IMG][/URL]

[URL='http://s679.photobucket.com/user/SnakePliskin2009/media/safe_image_zps400bbf04.jpg.html'][IMG]http://i679.photobucket.com/albums/vv155/SnakePliskin2009/safe_image_zps400bbf04.jpg[/IMG][/URL]

[URL='http://s679.photobucket.com/user/SnakePliskin2009/media/Arnie_zpsf31b0d13.jpg.html'][IMG]http://i679.photobucket.com/albums/vv155/SnakePliskin2009/Arnie_zpsf31b0d13.jpg[/IMG][/URL]

[MEDIA=youtube]aPnZxewFWyY[/MEDIA]

[MEDIA=youtube]c07KZ8mhUKg[/MEDIA]

[URL='http://www.muscleandfitness.com/october2013']Arnold Schwarzenegger in the October M&F! | Muscle & Fitness[/URL]

Which doesn't look double encoded.
 
Everything has displayed correctly in that post since I saw it earlier, so I'm not sure if that means it was fixed already. (I assumed that you had fixed it before posting.)
 
Everything has displayed correctly in that post since I saw it earlier, so I'm not sure if that means it was fixed already. (I assumed that you had fixed it before posting.)
Nope. I deliberately didn't edit it so you could see what was going on. After that, I *did* edit it and save without making any changes and I see this in the history (note I used firebug to increase the overlay height).
Obviously Xenforo has added quotes to the URLs, but I don't know why it wouldn't have done that when the post was originally created since we were using Xenforo then.
1.webp
 
So have you seen the proxy not working yourself (in this particular post)? How did you identify the errors as being from this post? From what I've seen, it's working correctly (the images are shown) so it seems like an erroneous report.

The quoting change is related to the WYSIWYG editor. Presumably the previous version wasn't created with the WYSIWYG editor or the BB codes were manually inserted.
 
So have you seen the proxy not working yourself (in this particular post)? How did you identify the errors as being from this post? From what I've seen, it's working correctly (the images are shown) so it seems like an erroneous report.

The quoting change is related to the WYSIWYG editor. Presumably the previous version wasn't created with the WYSIWYG editor or the BB codes were manually inserted.
No I haven't seen it failing myself except when I enter the URL reported by Google Webmaster Tools.
I did a search for that particular (correctly formatted) URL and that is the only post containing that URL in the forums.
Obviously there is worth in trying to eliminate the error 500s as reported by Google. This post is/was the source of one of them.
This is the complete list as reported on Google
proxy.php?image%3Dhttp%253A%252F%252Fi679.photobucket.com%252Falbums%252Fvv155%252FSnakePliskin2009%252FArnie_zpsf31b0d13.jpg%26hash%3De18819584ecb1587c9930eeeb48dd9d8
proxy.php?image%3Dhttp%253A%252F%252Fimg692.imageshack.us%252Fimg692%252F7658%252Fkxzs.jpg%26hash%3Dfab5303f7942a647dc68370e81a38595
proxy.php?image%3Dhttp%253A%252F%252Fwww.onlinesecurityproducts.co.uk%252Fuser%252Fproducts%252Flarge%252FINFP-KIT-WES.gif%26hash%3Db79601f085ea42d1fbac147872c09cdd
proxy.php?image%3Dhttp%253A%252F%252Ffarm4.static.flickr.com%252F3072%252F2975305027_91d1ee8036.jpg%26hash%3Dda6b623b2228a1400bf1efb2948512f1
proxy.php?image%3Dhttp%253A%252F%252Fi846.photobucket.com%252Falbums%252Fab28%252Flordingsy%252FSDC10573.jpg%26hash%3D9eb401c3d946b6eb5cd247309e2c3286
proxy.php?image%3Dhttp%253A%252F%252Fi57.photobucket.com%252Falbums%252Fg212%252Fkrish72%252Fb01qfs3z_366_206.jpg%26hash%3D7430770ec6ad96c409ca60d8e5134471
proxy.php?image%3Dhttp%253A%252F%252Fi50.tinypic.com%252Fx3u9s8.jpg%26hash%3D597e6edc4d42762c82a4650ab06bc7db
proxy.php?image%3Dhttp%253A%252F%252Fi43.tinypic.com%252F2zocgoj.jpg%26hash%3Dd688cfe81c72478a7c46e76aaf6cff5c
proxy.php?image%3Dhttp%253A%252F%252Fimg.photobucket.com%252Falbums%252Fv374%252FMarvdogger%252F800_sorcerer_12_blu-ray__zpsc2418e4e.jpg%26hash%3Daafc06448e03e2c9320b7a971d013694
proxy.php?image%3Dhttp%253A%252F%252Fimg835.imageshack.us%252Fimg835%252F4264%252F7665.jpg%26hash%3D7cdb95227891769d694c10167bc9c298
proxy.php?image%3Dhttp%253A%252F%252Fwww.hifidatabase.com%252Fstatic%252Fgallery%252F7%252F4577-Tannoy_SFX_5-1_sub_back.jpg%26hash%3D73cab59d9ffbf057adefb0c76c1a5387
which I guess end up being
 
It's possible the broken links are actually elsewhere. They may well be exactly what's in Google's output or they may have even been followed from another site; it's hard to say. With the links as presented, an error is expected. IMO, the only issue would be if there were direct steps to generate/insert links like that into XF (without some sort of especially convoluted process).
 
It's possible the broken links are actually elsewhere. They may well be exactly what's in Google's output or they may have even been followed from another site; it's hard to say. With the links as presented, an error is expected. IMO, the only issue would be if there were direct steps to generate/insert links like that into XF (without some sort of especially convoluted process).
Ok, fair enough Mike. The links were posted normally (rather than programmatically) so will have gone through the normal XF processing.
 
Top Bottom