Hopefully someone can explain some odd behavior I’ve encountered with jQuery. The following script is looking for relative links on my page and replacing them with absolute links.
$(document).ready(function() {
$("a[href^='/']").each(function(){
var cur_href = $(this).prop("href");
$(this).prop("href", 'http://www.mysite.com'+cur_href);
});
});
I’m using this script on a page that will be served up over https but I don’t want all of my navigation to link to https pages. Since my navigation are global includes, this seemed like the easiest way to fix the problem.
The issue I’m encountering comes in the actual replacement. The second line of the script correctly matches all relative links on the page and then runs the replacement part of the script. It is in the replacement, line 4, where I get some weird results. After this part of the script runs, my URLs end up looking like this:
Obviously isn’t doing what I want. It seems like the first part of the script is matching the relative URL but when the replacement part fires the browser has already tacked on the domain information.
The only thing I’ve found so far that actually does what I want is to write the replacement anticipating what the browser has tacked on:
this.href = this.href.replace(/^https:\/\/www\.mysite\.com\//, "http://www.mysite.com/");
Is there a better way to do this?
jQuery isn’t causing a problem here. The issue is that the
hrefproperty of HTMLAnchorElement (the type of object jQuery is returning), per the spec, always contains an absolute URI.In HTML5
hrefis a composite attribute and you can just swap the protocol (the part before//) at will by modifyinghref.protocol, e.g.:For older browsers without the composite
hrefyou’ll just have to make do with a regex:TLDR: Your code should look something like this:
P.S. You’ll notice that I elided your
$.eachcall. That’s becausepropautomatically acts on every element in the matched set, i.e. it already does what you were doing witheach.