gitea

tdsds.com/gitea

Fork 0

mirror of https://github.com/go-gitea/gitea synced 2025-12-07 13:28:25 +00:00

Commit Graph

Author	SHA1	Message	Date
Greg KarékinianandLauris BH	ebef3eff23	Remove a double slash in the HTTPS redirection when Let's Encrypt is enabled (#5537 ) Before: $ curl 0.0.0.0:3001 <a href="https://gitea.example.com:3000//">Found</a>. After: $ curl 0.0.0.0:3001 <a href="https://gitea.example.com:3000/">Found</a>. Fixes #5536	2018-12-12 23:00:24 +02:00
Greg Karékinianandtechknowlogick	15d6cf179d	Fix the Let's Encrypt handler by listening on a valid address (#5525 ) * Fix the Let's Encrypt handler by listening on a valid address Also handle errors in the HTTP server go routine, return a fatal error when something goes wrong. Thanks to @gbl08ma for finding the actual bug Here is an example of the error handling: 2018/12/11 14:23:07 [....io/gitea/cmd/web.go:87 func1()] [E] Failed to start the Let's Encrypt handler on port 30: listen tcp 0.0.0.0:30: bind: permission denied Closes #5280 * Fix a typo	2018-12-11 10:46:12 -05:00

Author

SHA1

Message

Date

Greg KarékinianandLauris BH

ebef3eff23

Remove a double slash in the HTTPS redirection when Let's Encrypt is enabled (#5537 )

Before:

$ curl 0.0.0.0:3001
<a href="https://gitea.example.com:3000//">Found</a>.

After:

$ curl 0.0.0.0:3001
<a href="https://gitea.example.com:3000/">Found</a>.

Fixes #5536

2018-12-12 23:00:24 +02:00

Greg Karékinianandtechknowlogick

15d6cf179d

Fix the Let's Encrypt handler by listening on a valid address (#5525 )

* Fix the Let's Encrypt handler by listening on a valid address

Also handle errors in the HTTP server go routine, return a fatal error
when something goes wrong.

Thanks to @gbl08ma for finding the actual bug

Here is an example of the error handling:

    2018/12/11 14:23:07 [....io/gitea/cmd/web.go:87 func1()] [E] Failed to
    start the Let's Encrypt handler on port 30: listen tcp 0.0.0.0:30: bind:
    permission denied

Closes #5280

* Fix a typo

2018-12-11 10:46:12 -05:00