View Single Post
Old 06-09-2020, 10:01 PM   #15
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,661
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
What if we tackled this from a different direction? Since nothing is actually being altered other than the url-encoding, can we detect whether the content has actually been modified and somehow skip the url encoding if it hasn't? As it is, it seems like the original content is always url encoded, and any new href (as a result of the renaming) is as well.

Surely there's a way that we can determine if--minus any url encoding--the content coming out is the same as the content that went in and either skip, or reverse the url encoding if nothing was actually updated?
DiapDealer is offline   Reply With Quote