From fd1081e0b0da95f38a19e91c7ab70a3193ea8f58 Mon Sep 17 00:00:00 2001
From: Frank Denis <github@pureftpd.org>
Date: Sun, 6 Jun 2021 22:50:50 +0200
Subject: [PATCH] up

---
 Cargo.toml |  2 +-
 README.md  | 11 ++++++++---
 2 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/Cargo.toml b/Cargo.toml
index 003944d..4508223 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -2,7 +2,7 @@
 name = "doh-proxy"
 version = "0.3.8"
 authors = ["Frank Denis <github@pureftpd.org>"]
-description = "A DNS-over-HTTPS (DoH) proxy"
+description = "A DNS-over-HTTPS (DoH) and ODoH (Oblivious DoH) proxy"
 keywords = ["dns","https","doh","proxy"]
 license = "MIT"
 homepage = "https://github.com/jedisct1/rust-doh"
diff --git a/README.md b/README.md
index 833f177..8b0bc97 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 # doh-proxy
 
-A fast and secure DoH (DNS-over-HTTPS) server.
+A fast and secure DoH (DNS-over-HTTPS) and ODoH (Oblivious DoH) server.
 
 `doh-proxy` is written in Rust, and has been battle-tested in production since February 2018. It doesn't do DNS resolution on its own, but can sit in front of any DNS resolver in order to augment it with DoH support.
 
@@ -29,12 +29,11 @@ cargo install doh-proxy --no-default-features
 ## Usage
 
 ```text
-A DNS-over-HTTPS (DoH) proxy
-
 USAGE:
     doh-proxy [FLAGS] [OPTIONS]
 
 FLAGS:
+    -O, --allow-odoh-post      Allow POST queries over ODoH even with they have been disabed for DoH
     -K, --disable-keepalive    Disable keepalive
     -P, --disable-post         Disable POST queries
     -h, --help                 Prints help information
@@ -109,6 +108,12 @@ It also provides DNS caching, server-side filtering, metrics, and TCP connection
 
 Unless the front-end is a CDN, an ideal setup is to use `doh-proxy` behind `Encrypted DNS Server`.
 
+## Oblivious DoH (ODoH)
+
+Oblivious DoH is similar to Anonymized DNSCrypt, but for DoH. It requires relays, but also upstream DoH servers that support the protocol.
+
+This proxy supports ODoH termination (not relaying) out of the box.
+
 ## Operational recommendations
 
 * DoH can be easily detected and blocked using SNI inspection. As a mitigation, DoH endpoints should preferably share the same virtual host as existing, popular websites, rather than being on dedicated virtual hosts.