3 ms·
Presumably the ideal use case here is for primarily client-side applications. However, it's worth pointing out that you'd never need to bind to every element in
by CGamesPlay 10y ago
Presumably the ideal use case here is for primarily client-side applications. However, it's worth pointing out that you'd never need to bind to every element individually because of event bubbling:
$('body').on('click', 'a', function() {
this.href += getToken();
});
- timtadh 10y agoProbably not the best idea to just tack the token onto the URL. There is a reason that people are not generally using tokens on URLs in lieu of cookies for session tokens. A better idea is to add a parameter in the POST body. This means that using this method all routes need a request body and you are therefore going to be mostly using POST in your API.
- albinowax_ 10y agoAgreed, definitely don't put a session token in the URL. I'd recommend using a custom HTTP header to transmit it - this way you aren't forced to use POST for everything.
- sametmax 10y agoDon't. People will copy/paste links. Better use an AJAX lib allowing a global override. Most of them allow it including the one in jquery and angular.