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

Request cannot be constructed from a URL that includes credentials #34847

Open
iatsiuk opened this issue Apr 10, 2019 · 3 comments
Open

Request cannot be constructed from a URL that includes credentials #34847

iatsiuk opened this issue Apr 10, 2019 · 3 comments
Labels

Comments

@iatsiuk
Copy link

@iatsiuk iatsiuk commented Apr 10, 2019

Kibana version: 6.7.1 Build: 20266

Elasticsearch version: 6.7.1

Server OS version: docker image based on node:carbon-alpine

Browser version: Google Chrome Version 73.0.3683.86 (Official Build) (64-bit)

Browser OS version: mac os 10.14.4 (18E226)

Original install method (e.g. download page, yum, from source, etc.): docker

Describe the bug:
Every time i see this error message:

Something went wrong 
Try refreshing the page. If that doesn't work, go back to the previous page or clear your session data. 

A Failed to execute 'fetch' on 'Window': Request cannot be constructed from a URL that includes credentials: /translations/en.json 

Screenshots (if relevant):
Screenshot 2019-04-10 at 12 38 20

@elasticmachine

This comment has been minimized.

Copy link
Contributor

@elasticmachine elasticmachine commented Apr 10, 2019

@joshdover

This comment has been minimized.

Copy link
Member

@joshdover joshdover commented Apr 22, 2019

@azasypkin this seems related to the changes in #34036. Any ideas here?

@azasypkin

This comment has been minimized.

Copy link
Member

@azasypkin azasypkin commented Apr 24, 2019

Hmm, passing user credentials in URL is a really bad idea and hence fetch doesn't support it and browsers will eventually drop support for this in other places as well:

If parsedURL includes credentials, then throw a TypeError.

We use fetch in many places, not only to load translations, so this approach will fall apart in another place anyway. But why do you need to use Kibana this way @iatsiuk ?

Generally if you want o bypass Login screen you should provide a Authorization: Basic *** or Authorization: Bearer *** HTTP header with every request (e.g. with the proxy in front of Kibana).

@azasypkin azasypkin removed the bug label Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.