Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in console when I'm opening the website with double slashes at the end of URL #7257

Closed
IgorOleniuk opened this issue Apr 22, 2020 · 5 comments

Comments

@IgorOleniuk
Copy link

IgorOleniuk commented Apr 22, 2020

Version

v2.12.2

Reproduction link

https://igora-dev-blog.herokuapp.com///

Steps to reproduce

Open an url with double slashes in the end

What is expected ?

Redirect to url without trailing slashes

What is actually happening?

When I'm opening the website with double slashes in URL I'm getting error in the console.

Error:
DOMException: Failed to execute 'replaceState' on 'History': A history state object with URL 'https:' cannot be created in a document with origin 'https://example.com' and URL 'https://example.com///'

Additional comments?

I don't understand why it's happening, how can I fix it?

@ghost ghost added the cmty:bug-report label Apr 22, 2020
@IgorOleniuk IgorOleniuk changed the title Error in console when trying to make redirect from trailing slashes Error in console when I'm opening the website with double slashes at the end of URL Apr 23, 2020
@AndrewSavetchuk
Copy link

I have the same issue on all my Nuxt.js projects

@pimlie
Copy link

pimlie commented May 14, 2020

See: vuejs/vue-router#2593

/cc @Atinux as you are the scrollBehaviour specialist (see this comment)

@stale
Copy link

stale bot commented Jun 14, 2020

Thanks for your contribution to Nuxt.js!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
  2. Comment the steps to reproduce it

Issues that are labeled as pending will not be automatically marked as stale.

@stale stale bot added the stale label Jun 14, 2020
@Atinux Atinux removed the stale label Jun 14, 2020
@stale
Copy link

stale bot commented Jul 31, 2020

Thanks for your contribution to Nuxt.js!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
  2. Comment the steps to reproduce it

Issues that are labeled as pending will not be automatically marked as stale.

@stale stale bot added the stale label Jul 31, 2020
@stale stale bot closed this as completed Aug 8, 2020
@RanjeetEppa18
Copy link

This issue still occurs on "nuxt": "^2.14.7"
Is this issue fixed in any version / workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants