Local HTTPS support
- Dominant language
- C#
- Stars
- 33
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I was trying to get aurelia to work with .net core 3.1 using this template with local HTTPS.
It works, but unfortunately I got a socket-js SSL error inside the browser console. After some research I found the following blogpost:
https://dnasir.com/2020/04/01/migrating-from-webpackdevmiddleware-to-spaservices-extensions/
Which describes the exact problem and solution. I tested the solution and it worked. Is it possible to make a fix for this. If you like I could make a pull request. The following changes are needed:
Inside [AureliaCliDevelopmentServer]https://github.com/aurelia/dotnet/blob/master/Aurelia.DotNet/AureliaCliDevelopmentServer.cs)
Row 99 change to:
` task => new UriBuilder("http", "127.0.0.1", task.Result).Uri);`
Inside webpack.config
` devServer: {
contentBase: outDir,
// serve index.html for all 404 (required for push-state)
historyApiFallback: true,
host: '127.0.0.1',
transportMode: 'ws'
},`
Thank you!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with Aurelia.DotNet/AureliaCliDevelopmentServer.cs around line 99 and the webpack.config devServer section named in the issue. Reproduce the local HTTPS setup with the .NET Core 3.1 template, then verify that the browser no longer reports the socket-js SSL error and that the requested configuration is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, webpack
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100