Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How to set https?
See original GitHub issueI used NSwag to generate Api documents. my website protocol is https, but NSwag still uses http
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
How to Enable HTTPS on Your Server - Best 2023 Tips
How to enable HTTPS on your server · 1. Buy an SSL certificate · 2. Request the SSL certificate · 3. Install the...
Read more >Enabling HTTPS on your servers - web.dev
Steps covered in this article · Enable HTTPS on your servers · Make intrasite URLs relative · Redirect HTTP to HTTPS ...
Read more >The Complete Guide To Switching From HTTP To HTTPS
The procedure is pretty much the same: Create a new certificate signing request, get a new HTTPS certificate, and install it on your...
Read more >How to enable HTTPS on your domain
In order to enable HTTPS on your website, you'll first need to purchase an SSL (Secure Sockets Layer) certificate from a reputable Certificate ......
Read more >How to enable HTTPs on Your Website in 2 minutes? - YouTube
Enable SSL Encryption on your site: Almost any website you visit today is protected by HTTPS. If yours isn't yet, it should be....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The scheme is set to the one from the request: https://github.com/RSuter/NSwag/blob/master/src/NSwag.AspNetCore/Middlewares/AspNetCoreToSwaggerMiddleware.cs#L96
You can change this in a PostProcess action or document processor (settings).
When running via cli then only AddSwaggerDocument is called, when starting as regular asp app both are called and the url/https stuff is overwritten in the use() call with the actual endpoint info and thus this has to be changed there. The document itself (except endpoint info) should be changed in add()