# HG changeset patch
# User Matt Harbison <matt_harbison@yahoo.com>
# Date 1675404479 18000
# Node ID 68cf519429effcf9a5f41513f86a7505c0aa9d0b
# Parent  ac93876ea2dff400ab05097ee5c32da210b7c395
hgweb: unbyteify the 100-continue check

The environment seems to be `str` or `tuple[int]`, and the same check in
`wsgicgi.py` is already `str` based, so I suspect this was wrong.  I think what
happened here is that the string wasn't `r''` prefixed in 482d6f6dba91 like
`wsgicgi.py`, so it got wrongly byteified in 687b865b95ad when converting to
byte literals en masse.

diff -r ac93876ea2df -r 68cf519429ef mercurial/hgweb/server.py
--- a/mercurial/hgweb/server.py	Mon Jan 30 18:50:11 2023 +0100
+++ b/mercurial/hgweb/server.py	Fri Feb 03 01:07:59 2023 -0500
@@ -203,7 +203,7 @@
         env['SERVER_PROTOCOL'] = self.request_version
         env['wsgi.version'] = (1, 0)
         env['wsgi.url_scheme'] = pycompat.sysstr(self.url_scheme)
-        if env.get('HTTP_EXPECT', b'').lower() == b'100-continue':
+        if env.get('HTTP_EXPECT', '').lower() == '100-continue':
             self.rfile = common.continuereader(self.rfile, self.wfile.write)
 
         env['wsgi.input'] = self.rfile