Commits
- 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:
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