Jump to content

Project Grandpa Jeep


Recommended Posts

EDIT: This forum software is phucking terrible. Pete get this fixed already. Not possible to copy and paste anything with an image tag.

EDIT 2: JFC, if you post with http it strips the image tag out, post with https it leaves the image tag, Pete why is it configured this way?

IMG_1346.jpg
IMG_1347.jpg
IMG_1348.jpg
IMG_1349.jpg
IMG_1350.jpg
IMG_1351.jpg
IMG_1352.jpg
IMG_1357.jpg

Have I said lately how happy I am with how these wheels turned out?

IMG_1373.jpg
IMG_1379.jpg

IMG_1385.jpg

Oh you sexy reflective beast:
IMG_1390.jpg
IMG_1391.jpg


IMG_1421.jpg
IMG_1429.jpg

IMG_1450.jpg

Surface rust:
IMG_1500.jpg
IMG_1510.jpg
IMG_1514.jpg
IMG_1518.jpg

 

 

Link to comment
Share on other sites

39 minutes ago, Sir Sam said:

EDIT 2: JFC, if you post with http it strips the image tag out, post with https it leaves the image tag, Pete why is it configured this way?

 

The short answer: http is dead

 

Prior to 2015 or so, webservers used both the http protocol (unencrypted transmission of data), and the https protocol (SSL/TLS-based encrypted transmission of data) to serve content.  Non-secure (http) connections were generally used when sensitive data was not present, and secure (https) connections were used when sensitive data was present.  Originally the Internet only used the http protocol, and https was added later once the need to encrypt data transmissions became apparent.  Due to overhead encrypting and decrypting data on older machines via https, only the data transmissions that needed to be encrypted were encrypted (hence the usage of both http and https URLs on websites up until around 2015).

 

In September of 2015 all the major browser makers began issuing warnings and disabling content loading on http-based websites.  In early 2016, the search engines started penalizing http-based sites in search rankings - giving priority to fully secure https-based sites.  By 2015 the overhead needed to encrypt and decrypt https transmissions was negligible due to advances in technology, and increased computing power.  Everybody started pushing to make websites fully secure, serving all pages with https (full SSL/TLS all the time).

 

In early 2019 all the major browser makers began failing to load content outright for http-based websites. 

 

At this point, software makers like Invision (who build this forum software) have began to include coding which prevents loading http-based resources into their software.  When you post an image link with an http-based URL at this point, the forum software basically looks at that like insecure junk and strips it.  It is insecure junk.  This site (comancheclub.com) runs full SSL all the time, all pages.  If you were actually able to include an http-based image into a forum post here, it wouldn't be displayed (or might be displayed after the browser issues tons of warnings during output of the page).  So the only valid URL for an image is an https-based URL, and if you copy/paste a valid image tag/URL into this forum software, it will do what you want.  Stay away from http-based URLs.

 

Further on this, due to the unreliability of remote image hosts (reference the PhotoBucket debacle from a couple of years ago), I'd highly recommend saving your images directly to comancheclub.com when making your post.  That puts the images you upload in this site's care, and I'm pretty sure @Pete M would never hold them for ransom, or shut the site down without notice, or limit your ability to get the images.

 

Now, back to your build thread - which is awesome...

Link to comment
Share on other sites

15 minutes ago, kryptronic said:

At this point, software makers like Invision (who build this forum software) have began to include coding which prevents loading http-based resources into their software.  When you post an image link with an http-based URL at this point, the forum software basically looks at that like insecure junk and strips it.  It is insecure junk.  This site (comancheclub.com) runs full SSL all the time, all pages.  If you were actually able to include an http-based image into a forum post here, it wouldn't be displayed (or might be displayed after the browser issues tons of warnings during output of the page).  So the only valid URL for an image is an https-based URL, and if you copy/paste a valid image tag/URL into this forum software, it will do what you want.  Stay away from http-based URLs.

 

So long story short, CC doesn't like http URLs because it thinks they are all insecure and not safe. It prefers https URLs because those are more secure, did I technology right?

Link to comment
Share on other sites

1 hour ago, kryptronic said:

 

The short answer: http is dead

 

Further on this, due to the unreliability of remote image hosts (reference the PhotoBucket debacle from a couple of years ago), I'd highly recommend saving your images directly to comancheclub.com when making your post.  That puts the images you upload in this site's care, and I'm pretty sure @Pete M would never hold them for ransom, or shut the site down without notice, or limit your ability to get the images.

 

Now, back to your build thread - which is awesome...

 

Fine so be it. This is the only forum I have encountered that has issues with the HTTP, though admittedly I'm not sure how I managed to grab the non secure link in the first place. 

 

I prefer to keep images hosted on my website. After all I've had my site around since before CC existed. :D

Link to comment
Share on other sites

5 hours ago, 89 MJ said:

So long story short, CC doesn't like http URLs because it thinks they are all insecure and not safe. It prefers https URLs because those are more secure, did I technology right?

 

Technically what you wrote is incorrect, however you understood it well enough :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...