In bug 2004679 comment 4, janbrasna observed that the `rv:` in Firefox's UA string seems to trigger a UA-sniffing-based-blockage in some ASP.NET backend (possibly due to being miscategorized as IE11, which also included `rv:`). Apparently no other modern browser has `rv:` in their UA string, and IE used to have it, so sites might take it as a sign of your browser being IE. Perhaps we should remove/reformat that portion of our UA string, to take a step closer to other modern browsers' UA-string-formatting (and a step away from IE's formatting), to avoid inadvertently tripping over this sort of UA-string-based block? (Note, I don't know offhand if bug 2004679 was a one-off at just a single site vs. a sign of something broader where other sites reuse the same logic. So we may only want to take action if we find evidence of this happening on other sites beyond the one in bug 2004679.) [Note: I'm filing this in Networking:HTTP to match the other UA-string-tweak bugs that I found - e.g. bug 1861847. Feel free to reclassify if there's a better spot for this]
Bug 2032198 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In bug 2004679 comment 4, janbrasna observed that the `rv:` in Firefox's UA string seems to trigger a UA-sniffing-based-blockage in some ASP.NET backend (possibly due to being miscategorized as IE11, which also included `rv:`). Apparently no other modern browser has `rv:` in their UA string, and IE used to have it, so sites might take it as a sign of your browser being IE. Perhaps we should remove/reformat that portion of our UA string, to take a step closer to other modern browsers' UA-string-formatting (and a step away from IE's formatting), to avoid inadvertently tripping over this sort of UA-string-based block? (Note, I don't know offhand if bug 2004679 was a one-off at just a one-off issue affecting only that single site, vs. a sign of something broader where more sites might have the same logic via some shared tool/library. So we might not want to take any action here, unless/until we find evidence of this impacting other sites beyond the one in bug 2004679.) [Note: I'm filing this in Networking:HTTP to match the other UA-string-tweak bugs that I found - e.g. bug 1861847. Feel free to reclassify if there's a better spot for this]