Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
caddy
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
caddy
Commits
151d0baa
Commit
151d0baa
authored
Aug 23, 2016
by
Matthew Holt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor text fixes ;)
parent
9d947713
Changes
5
Hide whitespace changes
Inline
Side-by-side
Showing
5 changed files
with
12 additions
and
3 deletions
+12
-3
CONTRIBUTING.md
CONTRIBUTING.md
+2
-1
README.md
README.md
+1
-1
caddyhttp/redirect/setup.go
caddyhttp/redirect/setup.go
+1
-1
caddytls/config.go
caddytls/config.go
+3
-0
caddytls/crypto.go
caddytls/crypto.go
+5
-0
No files found.
CONTRIBUTING.md
View file @
151d0baa
...
...
@@ -65,7 +65,8 @@ Don't worry, that won't happen without an open discussion first.
If you are going to spend significant time writing code for a new pull request,
best to open an issue to "claim" it and get feedback before you invest a lot of
time.
time. Not all pull requests are merged, and that's okay.
[
Read why.
](
https://github.com/turbolinks/turbolinks/pull/124#issuecomment-239826060
)
Remember: pull requests should always be thoroughly documented both via godoc
and with at least a rough draft of documentation that might go on the website
...
...
README.md
View file @
151d0baa
...
...
@@ -99,7 +99,7 @@ Note: You will need **[Go 1.6](https://golang.org/dl/)** or newer.
1.
`go get github.com/mholt/caddy/caddy`
2.
`cd`
into your website's directory
3.
Run
`caddy`
(assum
es
`$GOPATH/bin`
is in your
`$PATH`
)
3.
Run
`caddy`
(assum
ing
`$GOPATH/bin`
is in your
`$PATH`
)
Caddy's
`main()`
is in the caddy subfolder. To recompile Caddy, use
`build.bash`
found in that folder.
...
...
caddyhttp/redirect/setup.go
View file @
151d0baa
...
...
@@ -165,5 +165,5 @@ var httpRedirs = map[string]int{
"304"
:
http
.
StatusNotModified
,
"305"
:
http
.
StatusUseProxy
,
"307"
:
http
.
StatusTemporaryRedirect
,
"308"
:
308
,
// Permanent Redirect
"308"
:
308
,
// Permanent Redirect
(RFC 7238)
}
caddytls/config.go
View file @
151d0baa
...
...
@@ -130,6 +130,9 @@ func (c *Config) ObtainCert(allowPrompts bool) error {
return
c
.
obtainCertName
(
c
.
Hostname
,
allowPrompts
)
}
// obtainCertName gets a certificate for name using the ACME config c
// if c and name both qualify. It places the certificate in storage.
// It is a no-op if the storage already has a certificate for name.
func
(
c
*
Config
)
obtainCertName
(
name
string
,
allowPrompts
bool
)
error
{
if
!
c
.
Managed
||
!
HostQualifies
(
name
)
{
return
nil
...
...
caddytls/crypto.go
View file @
151d0baa
...
...
@@ -106,6 +106,11 @@ func stapleOCSP(cert *Certificate, pemBundle []byte) error {
}
}
else
{
// invalid contents; delete the file
// (we do this independently of the maintenance routine because
// in this case we know for sure this should be a staple file
// because we loaded it by name, whereas the maintenance routine
// just iterates the list of files, even if somehow a non-staple
// file gets in the folder. in this case we are sure it is corrupt.)
err
:=
os
.
Remove
(
ocspCachePath
)
if
err
!=
nil
{
log
.
Printf
(
"[WARNING] Unable to delete invalid OCSP staple file: %v"
,
err
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment