<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8">Hi,<div><br></div><div>do you forward all headers the browser sends to the server?</div><div>The chrome version is very old.</div><div>You need to pretend that you are the browser.</div><div><br></div><div>Kind regards,</div><div>Manuel</div><div><br></div><div><br></div><div><br></div><div><div dir="ltr"><br><blockquote type="cite">Am 03.02.2023 um 08:54 schrieb Lukas Tribus <lukas@ltri.eu>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><br><br>On Friday, 3 February 2023, Saint Michael <<a href="mailto:venefax@gmail.com">venefax@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have a reverse proxy but the newspaper that I am proxying is<br>
protected by cloudflare, and the block me immediately, even if I use a<br>
different IP. So somehow they know how to identify my reverse-proxy.<br>
How is my request different than a regular browser? What is giving me up?<br>
can somebody give an example of what are the rules so my proxy passes<br>
for a regular person?</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
</blockquote><div><br></div><div>OS fingerprinting, TLS fingerprinting, H2/H3 feature fingerprinting.</div><div><br></div><div>You will not beat Cloudflare anti bot functionality with a few nginx settings... this is a rabbit hole.</div><div><br></div><div><br></div><div><br></div><div><br></div>
<span>_______________________________________________</span><br><span>nginx mailing list</span><br><span>nginx@nginx.org</span><br><span>https://mailman.nginx.org/mailman/listinfo/nginx</span><br></div></blockquote></div></div></div></body></html>