Trailing slash always appended to URL before state parameters

[jasonhill]

Hi,

The standard for our site is to remove trailing slashes in URLs with a permanent redirect. However, the History control seems to be always appending a slash before the state parameters. Shouldn't it just be looking at the current URL and appending the state parameters rather than always assuming a trailing slash?

Is there any way to control that behaviour?

Thanks,

Jason

[longlostnick]

Having the same problem. This broke my rails app routes because of the "unix" style paths

[jasonhill]

I ended up editing the js to stop it appending the trailing slash.

[longlostnick]

i tried that too, but ultimately ended up going w bbq.js because all i needed was the basics anyway. didnt really look too closely but maybe bbq can do all the stuff this does anyway. worth looking at if youre still having trouble.

[jasonhill]

I think I looked at bbq but it just uses the hash rather than querystring right?

[longlostnick]

Yep, I believe that was the difference.

[AntonKast]

If your page URL is http://example.com/page, try calling pushState() with a url like "page?parameter".

[tomthetree]

+1 @AntonKast - This is the solution, solved it for me.

[joeferraro]

+1 @AntonKast

[AaronLayton]

@AntonKast the solution works, but we should get this changed so it doesn't keep adding it on. As @jasonhill said we should be able to control this currently doesn't mimic the history api

[matteopoile]

I agree with @AaronLayton

[mhlavac]

Any news on this issue?

When I use query to define new location it adds trailing slash which doesn't make sense. There could be an option to enable/disable this behavior.

What do you think?

[AaronLayton]

+1

[verdet23]

+1

[pensiero]

+1

[jwynveen]

+1

[MiguelRipoll23]

+1

[michelkusters]

+1

[MiguelRipoll23]

I forgot to say that it only happens to me when domain is localhost.

[michelkusters]

This piece of code might be useful for some.

var href = $(this).prop("href");
History.pushState(null, null, href);

[juliosantos]

+1

[jenkek]

@mhlavac :+1:

[aSchimp]

+1

[ProPuke]

2017 now passing...

[tristanjthompson]

2019 now passing...

[AaronLayton]

Is this issue still a problem in 2019? Unless we are stuck supporting older, non-evergreen browsers etc.

[Manish-Solanki]

Instead change the logic where trialling '/' is invalid

Ex. In case there is request parameters too - https://www.xxxx.xxx/customer/?city=delhi // This is invalid case where /? should not together Best suitable solution would be replace trialling slash with .replace(//$/, '')

Code : else if ( firstChar === '?' ) { // Query URL fullUrl = History.getPageUrl().replace(//$/, '').replace(/[?#].*/,'')+url; }

After change: https://www.xxxx.xxx/customer?city=delhi

[Peter080202]

I forgot to say that it only happens to me when domain is localhost.

Hi, did you find any workaround or solution for this? @MiguelRipoll23