If I’m fetching from a server via the Apache client, it follows redirects, but if I connect direct i...

# http4k

[dmcg]

If I’m fetching from a server via the Apache client, it follows redirects, but if I connect direct in memory it doesn’t. Is there any existing way (a filter;-) of making in-memory work the same way?

[dave]

ClientFilters.FollowRedirects

[dmcg]

Lucky guess

[dave]

It's aways a filter!

[s4nchez]

@dmcg is the http4k-apache client following redirects by default? We usually turn those off so we don't depend on the client-specific implementation

[dave]

you can make a fake browser by doing

val handler = ClientFilters.FollowRedirects()
        .then(ClientFilters.Cookies(storage = cookieStorage()))
        .then(ApacheClient())

It's how we test oauth flows in memory 🙂

[dmcg]

I don’t suppose there’s a ClientFilters.Cookie Store?

[dmcg]

Dammit, beat me to it

[dave]

you will also need to put a reverseProxy in so that the redirect goes to the "other" handler" if there is one

[dmcg]

Mind reading support

[dave]

the short answer is that THERE IS ALWAYS A FILTER (or similar 🙂 )

[dave]

Mind reading support

And all for one low low price!

[dave]

you're all so damn predictable

[dmcg]

Haddock

[dave]

ServerFilters.BestFishForFrying()