So, I was looking at post #2263546 and tried the source link https://yellow.ribbon.to/~pukarin/gallery/01mgxby/mnms01.htm

It didn't work and after bashing my head against the keyborad for a couple minutes I figured that if I replaced https with http the source link would work.

I then tried updating said source link with this change but e621 autocorrects the link back to https.

The link IS correct, and I am aware that https is more secure than http, but for this case https does not work. Is there anything that can be done about this?

salvadorjoao said:
So, I was looking at post #2263546 and tried the source link https://yellow.ribbon.to/~pukarin/gallery/01mgxby/mnms01.htm

It didn't work and after bashing my head against the keyborad for a couple minutes I figured that if I replaced https with http the source link would work.

I then tried updating said source link with this change but e621 autocorrects the link back to https.

The link IS correct, and I am aware that https is more secure than http, but for this case https does not work. Is there anything that can be done about this?

For now, have to put a note in description, I guess. In theory, those sites could have an exception in the script that autorenames?

alphamule said:
For now, have to put a note in description, I guess. In theory, those sites could have an exception in the script that autorenames?

Tried bashing my head against it one more time with the help of a friend. Embeding exceptions into the link does not seem to work.

He also said that an exception to these kinds of site would be unlikely, but then again I'm not tech savy enough to acertain that as a definitive conclusion.

So for the time being, a warning in the description will be the best bet.