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.

Sign up for GitHub

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

Jump to bottom

ServiceWorker.register should reject a Promise for unsecure urls #1411

Closed
miherlosev opened this issue Dec 8, 2017 · 1 comment
Closed

ServiceWorker.register should reject a Promise for unsecure urls #1411

miherlosev opened this issue Dec 8, 2017 · 1 comment
Labels
AREA: client !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Milestone
Sprint #10

Comments

@miherlosev
Copy link
Contributor

Reproduced on http://skanska-poc-react.azurewebsites.net/login

Secure origins:

(https, *, *)
(wss, *, *)
(*, localhost, *)
(*, 127/8, *)
(*, ::1/128, *)
(file, *, —)
(chrome-extension, *, —)

From https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features
@miherlosev miherlosev added this to the Sprint #10 milestone Dec 8, 2017
@miherlosev miherlosev assigned miherlosev and unassigned miherlosev Dec 8, 2017
LavrovArtem added a commit to LavrovArtem/testcafe-hammerhead that referenced this issue Dec 8, 2017
@LavrovArtem
fix ServiceWorker.register should reject a Promise for unsecure urls (
90af48b 
close DevExpress#1411)
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
@LavrovArtem @AndreyBelym
fix ServiceWorker.register should reject a Promise for unsecure urls (
57f4f42 
close DevExpress#1411) (DevExpress#1413)

* fix `ServiceWorker.register should reject a Promise for unsecure urls` (close DevExpress#1411)

* fix review's issues

* remove 'chrome-extension:' protocol
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
AREA: client !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Milestone
Sprint #10
Development

No branches or pull requests
1 participant
@miherlosev