Todd Menier

@Marusyk Sometimes it's a fine line between a breaking change and fixing some unintended behavior seems "obviously" quirky/buggy. I logged this because I bumped into it in a real-world scenario...

I was hoping I could piggyback off existing code to fix this but it's a little trickier than I thought. I'm considering adding `AppendQueryParam(s)` that, unlike `SetQueryParam(s)`, don't overwrite. With...

Although I still think this seems like an obvious quirk, now that I'm pushing it out to 4.0 I'll play it safe and call it breaking. #688 will be a...

> Not all responses can be purely static, some are dynamic based on the request. I'm not sure I agree with your premise, because we're specifically within the context of...

That makes sense. Could be scenarios where this simplifies test setup too. I don't know that I love how `RespondWith` deals with raw `HttpRequestMessage` and `HttpResponseMessage` since Flurl provides wrappers,...

Have you tried reversing the order of those setup calls? Think of `ForCallsTo` as adding match conditions to a list (because it literally does that), and when a call is...

Sorry for the delay and hopefully you found some kind of work-around for this by now, but the extra info you provided is helpful. Basically, `AllowRealHttp` does not cause Flurl...

I'll actually keep this open for my own tracking purposes. There will tentatively be "a" fix for this of some sort, at some point. :)

Doing a little spring cleaning and I see this slipped through the cracks long ago. Looks like you solved it for your case but I imagine it's still an "issue"...

I'll look into this for 4.x. I can't claim that Flurl is OAuth-agnostic since it already has `WithOAuthBearerToken`, so taking a step deeper into that water doesn't seem totally unreasonable....