HTTP authorization

[tofuproxy.git] / doc / index.texi

diff --git a/doc/index.texi b/doc/index.texi
index 7759710db9072ac1680b4537399fd194ebbac836..be8e76f0ec7a92aacd6837bb91ea9668d8f97b2c 100644 (file)
--- a/doc/index.texi
+++ b/doc/index.texi
@@ -34,6 +34,8 @@ extensions for that.
 kind of @url{https://en.wikipedia.org/wiki/Privoxy, Privoxy}, but it is
 not friendly with TLS connections, obviously.
 
+@item Xombrero sometimes has problems with HTTP-based authorization.
+
 @item Hardly anyone does
 @url{https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities, DANE}
 checks.
@@ -91,6 +93,10 @@ creating some kind of complex configuration framework.
 @item Even when native Go's checks are failed, you can still make a
     decision to forcefully trust the domain.
 
+@item HTTP-based unauthorized responses are intercepted and
+    user/password input dialog is shown. It automatically loads initial
+    form values from @file{.netrc}.
+
 @item Optionally DANE-EE check is also made for each domain you visit.
 
 @item TLS session resumption and keep-alives are also supported.
@@ -101,16 +107,3 @@ creating some kind of complex configuration framework.
 @end itemize
 
 @include usage.texi
-
-@node TODO
-@unnumbered TODO
-
-What I am planning possibly to do? Just brainstorming:
-
-@itemize
-
-@item HTTP authorization dialog.
-
-@item TLS client certificates usage capability.
-
-@end itemize