Commits
- Commit:
b7967bc1f695126e1bf2705bfd486bbc32aaf8b0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
proxy: allow multiple proxy blocks, matching options and validations
as a side effect the order of the content of a server block is relaxed:
options, location or proxy blocks can be put in any order.
- Commit:
e2f167afb3444d3ba55fdffe234ef7812cac72f0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
bump copyright year :)
- Commit:
593e412b4988ca8b72bb7ef9b1cc663cb1184215
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow to disable TLS when proxying requests
- Commit:
294a57275af3dafa948119e60a8db979be25e1f7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move %token USER to its own line
- Commit:
3c4b712bb2ef520be964da95fd627060f6639bf8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
plug some memory leaks in config parsing
I forgot to free some strings when they're no more used.
- Commit:
c7c8ef448bc8832998606ec217907c7dc66fec6c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add `protocols' option to `proxy' rule
- Commit:
5128c0b0e3b51737783c4c68c9e34a76ec8c8b0e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add `verifyname' option for `proxy' rule
- Commit:
7bdcc91ec70ddde092ac5d7b4f75d54915e7b221
- From:
- Omar Polo <op@omarpolo.com>
- Date:
simplify the proxying code
it doesn't make any sense to keep the proxying info per-location:
proxying only one per-vhost. It can't work differently, it doesn't make
sense anyway.
- Commit:
d49093c105e7e9af2638bce945374ac0036b3498
- From:
- Omar Polo <op@omarpolo.com>
- Date:
support optional client certificate for proxy rule
- Commit:
da2185f37f70f8665c4d800f8f9bbf4027fd7b81
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move proxy sub-options to their own rule and allow grouping with { ... }
- Commit:
72b033ef18ae3f82922f6f11ce0f5194e95f667d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add ability to proxy requests
Add to gmid the ability to forwad a request to another gemini server and
thus acting like a reverse proxy. The current syntax for the config
file is
server "example.com" {
...
proxy relay-to host:port
}
Further options (like the use of custom certificates) are planned.
cf. github issue #7
- Commit:
ff05125eb81e5bbf2cf05b8434d03bce584936e0
- From:
- Stephen Gregoratto <dev@sgregoratto.me>
- Via:
- omar-polo <op@omarpolo.com>
- Date:
Implement OCSP stapling support
Currently dogfooding this patch at gemini.sgregoratto.me. To test,
run the following command and look for the "OCSP response" header:
openssl s_client -connect "gemini.sgregoratto.me:1965" -status
- Commit:
f0a01fc742e83b3f4736b5d64af3ab18148afc5a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
two -n to dump the parsed configuration
This adds a barebone dumping of the parsed configuration. It is not
complete, but I'm interested in dumping the full path to `cert' and
`key' in order to write some scripts that can inspect the
configuration, extract the certificates and renew them when expired
automatically.
It's not easy to parse gmid configuration otherwise because the syntax
is flexible and users can use macros. Instead, the idea is to run
gmid and let it dump the configuration once it's been parsed in a
static and predictable format.
Now is possible to parse gmid configuration with, say, awk or perl.
- Commit:
83272dfee9eb5292ce21de55ebdbb3876a37fcb1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't yyerror if we can't open the file
the global var file could still be NULL and yyerror would crash.
- Commit:
abc8801d6064304c627cd75ed1f8c585d51346de
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo