TestCafe throws the "Only secure origins are allowed" DOMException

anon98470090 2018-04-23 09:53:38 UTC #1

Hi there.

Usually, I use URL, http://localhost:3000/ in local machine.
but, when TestCafe is running, it automatically modify pre-URL like http://192.168.1.47:50606/p6ISMkxMW

so, whole url is http://192.168.1.47:50606/p6ISMkxMW/http://localhost:3000/.
Could you tell me how to remove such as strange URL?

MarinaRukavitsyna 2018-04-23 11:27:20 UTC #2

Hi @moffsugita,
This behavior is caused by the fact that TestCafe uses a URL-rewriting proxy196 under the hood. You can learn about this in detail in the following sources:

TestCafe: An e2e Testing Tool That Doesn’t Use Selenium
Why not use Selenium

anon98470090 2018-04-25 01:13:00 UTC #3

Hello @MarinaRukavitsyna

Thank you for response.
So, I can't remove URL-rewriting proxy URL?

Why the gif animation didn't use URL-rewriting proxy URL? it is 10.10.102.236 only

anon98470090 2018-04-25 05:25:57 UTC #4

Why I want to remove URL-rewriting proxy URL is that the server return 404 page when TestCafe is running.
I guess the server deny proxy.
Or, is it able to fix proxy port number?

anon98470090 2018-04-25 05:51:00 UTC #5

I found --ports option.
but it is 2 args. I used --ports 50606,50607.
However, removed s option --port can't work...

MarinaRukavitsyna 2018-04-25 07:12:19 UTC #6

No, it is impossible to modify URL. This is how TestCafe and URL-rewriting proxy work. Would you please clarify why you wish to delete it? Have you encountered any issue with this URL when testing your app? If so, would you please describe it in greater detail so that we can check for a possible solution?

This is how Safari works. It always shows a host only. If, however, you click the address bar, Safari will show the entire URL as well.

anon98470090 2018-04-25 07:47:20 UTC #7

Would you please clarify why you wish to delete it?

When I run local server it returns success,
http://192.168.1.47:50606/p6ISMkxMW/http://localhost:3000/.

but Amazon S3 server returns 404.
http://192.168.1.47:50606/p6ISMkxMW/https://myserver.com/.

After much consideration, I guess URL string was not the bottom cause. So, I don't need to delete.
I found error in console of Chrome.

hammerhead.js:2 Error during service worker registration: DOMException: Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).

hammerhead.js is URL-rewriting proxy module(?).

This is how Safari works.

I see.

anon98470090 2018-04-25 08:19:08 UTC #8

service worker registration

My React App was created by create-react-app tool.
It create first templates for React App.
It has registerServiceWorker method.
It may disturb

github.com

wmonk/create-react-app-typescript/blob/master/packages/react-scripts/template/src/registerServiceWorker.ts

// tslint:disable:no-console
// In production, we register a service worker to serve assets from local cache.

// This lets the app load faster on subsequent visits in production, and gives
// it offline capabilities. However, it also means that developers (and users)
// will only see deployed updates on the 'N+1' visit to a page, since previously
// cached resources are updated in the background.

// To learn more about the benefits of this model, read https://goo.gl/KwvDNy.
// This link also includes instructions on opting out of this behavior.

const isLocalhost = Boolean(
  window.location.hostname === 'localhost' ||
    // [::1] is the IPv6 localhost address.
    window.location.hostname === '[::1]' ||
    // 127.0.0.1/8 is considered localhost for IPv4.
    window.location.hostname.match(
      /^127(?:\.(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)){3}$/
    )
);

This file has been truncated. show original

anon98470090 2018-04-25 08:53:34 UTC #9

Failed to load resource: the server responded with a status of 400 (Bad Request)
http://192.168.1.47:53851/prY2ujt12/https://cognito-idp.us-east-2.amazonaws.com/

the error also appeared.

MarinaRukavitsyna 2018-04-25 11:22:08 UTC #10

It looks like you have encountered the issue described in the following thread:

Run testcafe with https protocol

You can also try running Chrome with arguments:

StackOverflow: Why am I seeing “Error - Only secure origins are allowed” for my service worker?
TestCafe: Starting browser with arguments

anon98470090 2018-04-26 01:01:40 UTC #11

@MarinaRukavitsyna
Thank you for replying.
TestCafe can open browser with parameter?

anon98470090 2018-04-26 05:33:58 UTC #12

I guess the casuse is S3's BucketPolicy settings.

MarinaRukavitsyna 2018-04-26 11:31:09 UTC #13

TestCafe can open browser with parameter?

Yes, please refer to the following help topic that describes how to run a browser with parameters:

TestCafe: Starting browser with arguments