could this be optional? I don't feel that changing your agent necessarily means you want to cache both versions, but this is enforcing it. I think you will also need to move force_feed to your options array, because you could end up with two # segments in the url.

1. Yes, we can make an option if you want. I am not sure what use-case would be addressed by such an option though. In any case, I think it would be more standard and less error prone to not share cache by default. As standard, HTTP caches are not supposed to be shared with different query parameters, and should even obey things such as Vary in the response. If you confirm that you rather want an option, and if yes what the default should be, I will edit accordingly.

2. Extra hashes are legal in an URL fragment, e.g. https://example.net/#one#two#three . See e.g. https://tools.ietf.org/html/rfc3986#appendix-B , any character is allowed after the first hash sign. The corresponding PHP function parses it just fine:

<?php
$url = 'https://example.net/#one#two#three';
print_r(parse_url($url));

Array
(
    [scheme] => https
    [host] => example.net
    [path] => /
    [fragment] => one#two#three
)

ok fair enough, I was thinking caches might grow unexpectedly from this change but that's really only a problem if you're changing the agent options a lot. thanks for the update!