Regression: SWA 1.0.3 server crash while running https and proxy to https frontend (tested with self signed cert)

[eltorio]

Are you accessing the CLI from the default port :4280 ?

• [x] No, I am using a different port number (--port) and accessing the CLI from that port
• [ ] Yes, I am accessing the CLI from port :4280

Make sure you are accessing the URL printed in the console when running swa start!

ℹ️ NOTE: Make sure to enable debug logs when running any swa commands using --verbose=silly

Describe the bug Regression BUG with swa 1.0.3 server crash while proxied to frontend server with https self signed certificate

To Reproduce

git clone https://github.com/highcanfly-club/azure-swa-clib-bug-580.git
cd azure-swa-clib-bug-580
git checkout 1.0.3
npm i
npm start
# browse to https://localhost:8788

Expected behavior A working server 1.0.2 was OK

git clone https://github.com/highcanfly-club/azure-swa-clib-bug-580.git
cd azure-swa-clib-bug-580
git checkout 1.0.2
npm i
npm start
# browse to https://localhost:8788

Desktop (please complete the following information):

• OS: MacOS
• Version 13.0 (22A5365d)
• NodeJS 16.17.1

Additional context swa 1.0.3

[eltorio]

oups I forgot to push the branches 1.0.2 and 1.0.3 to github ! Now it is ok 1.0.2 https://github.com/highcanfly-club/azure-swa-clib-bug-580/tree/1.0.2 1.0.3 https://github.com/highcanfly-club/azure-swa-clib-bug-580/tree/1.0.3

[manekinekko]

Thanks @eltorio for reporting this issue. We'll investigate it and update you asap.

[eltorio]

Hi, @manekinekko Thank you for listening to our problems :)

this is the latest lines of the silly log on 1.0.3 after browsing to https://localhost:8788

[swa] ------------------- processing route -------------------
[swa] --------------------------------------------------------
[swa] processing /
[swa] checking for matching route
[swa] check if request match route
[swa]  - route: /!*
[swa]  - wildcard: true
[swa] checking wildcard route
[swa]  - glob: /!*
[swa]  - pathBeforeWildcard: /!
[swa]  - base path doesn't match. Exit
[swa]  - alternateRequestPath: /index.html
[swa] checking wildcard route
[swa]  - glob: /!*
[swa]  - pathBeforeWildcard: /!
[swa]  - base path doesn't match. Exit
[swa] checking auth request
[swa]  - not an auth request
[swa] checking function request
[swa]  - not a function request
[swa] checking HTTP method: GET
[swa]  - method is valid (allow-list: GET,HEAD,OPTIONS)
[swa] checking for query params
[swa] checking rewrite auth login request
[swa] checking rewrite auth logout request
[swa] checking authorizations for route
[swa]  - no matching rule
[swa]  - access authorized
[swa] using userConfig
[swa] - userConfig:
[swa]  - globalHeaders:
[swa]    - content-security-policy: default-src https: 'unsafe-eval' 'unsafe-inline'; object-src 'none'
[swa]  - routes:
[swa]   - 0:
[swa]     - route: /!*
[swa]     - rewrite: /api/redirect
[swa] checking storage content
[swa] remote dev server detected.
[swa]  - url: /
[swa]  - target: https://localhost:5173
[swa] customUrl: false
[swa] is4xx: false
[swa] remote dev server detected. Proxying request
[swa]  - url: /
[swa]  - code: 200
[swa] GET https://localhost:5173/ (proxy)
[swa] killing SWA CLI
[swa] node "/Users/---/Development/azure-swa-clib-bug-580/node_modules/@azure/static-web-apps-cli/dist/msha/server.js" exited with code 0
--> Sending SIGTERM to other processes..
[api] [2022-10-10T06:51:38.915Z] Language Worker Process exited. Pid=66314.
[api] [2022-10-10T06:51:38.915Z] node exited with code 143 (0x8F). .
[run] cd "/Users/---/Development/azure-swa-clib-bug-580" && npm run dev exited with code SIGTERM
--> Sending SIGTERM to other processes..
[api] [2022-10-10T06:51:39.044Z] Worker 3bcb5ac9-7c5f-4f1e-8c1a-803005bd4176 connecting on 127.0.0.1:51186
[api] [2022-10-10T06:51:39.092Z] Received WorkerInitRequest
[api] [2022-10-10T06:51:39.096Z] Worker process started and initialized.

Full log is in the 1.0.3 branches of the testing repo https://github.com/highcanfly-club/azure-swa-clib-bug-580/blob/1.0.3/silly_after_browsing_to_https_localhost_8788.log

[eltorio]

oups! log wasn't full because the terminal buffer was too short, it is corrected now

[sgollapudi77]

@eltorio please feel free to track this issue at #610. Closing this issue now