Add more filters about spring-cloud-gateway HOT 19 CLOSED

I'm working on filters that rewrite request/response body.

Now they successfully work with string body, url encoded, json objects.

In plans to add support of multipart/form-data and sse post-processing to complete the set of data conversions how it has been done in Spring Webflux handlers concerning codecs and readers/writers.

See comment.

Have you interest?

from spring-cloud-gateway.

@spencergibb
Ok, after I will finish text-stream-based response rewritting, I'm going to prepare code to PR and release it. At the moment I have to deepen my Flux knowledge to solve it - I'm being in reading docs... After this, the form-multipart rewritting remains, I hope I will also do it. The progress can be viewed here. Any comments or suggestions are welcome.

from spring-cloud-gateway.

I'm working with Rate limiters too via filters. I really want to have the 3 prong approach we see here: https://stripe.com/blog/rate-limiters working with a Spring Cloud project.

from spring-cloud-gateway.

I have a concurrent request rate limiter implemented on Redis using the same model as RedisRateLimiter and the Stripe rate limiters. Before I spend time prepping the code for a pull request, I'd like to know if there is interest?

Thanks

from spring-cloud-gateway.

See 0105e57 for sample token-bucket filter.

from spring-cloud-gateway.

I'll take a look

from spring-cloud-gateway.

Nice, lots of code too!

from spring-cloud-gateway.

@checketts check out 34e6366.

from spring-cloud-gateway.

Wow that looks very clean with good potential for extensibility eventually. The Lua part scares me a bit since I don't understand how that integrates or changes the atomicity of the redis call.

I've been trying to reason through a non-redis implementation, likely Memcached. Would porting the Lua code into Java client code be sufficient?

from spring-cloud-gateway.

https://redis.io/commands/eval#atomicity-of-scripts

I like that this is run in production at stripe.

from spring-cloud-gateway.

Looking to migrate off our commercial gateway (CA). Main features we use today are for SOAP services would there be anything to re-implement those:

• Require/Add WS-Security Signature, Signed Timestamp/Element
• Evalute XPATH, XSLT
• Protect against Message Reply

We use SpringWS but these were not extensively supported but possible in the WSS4j side. Looking if it's an easy switch over to CXF (3.2) that supports Spring Boot.

from spring-cloud-gateway.

@sbartram if you're talking about the "Concurrent Request Rate Limiter" from https://stripe.com/blog/rate-limiters, then yes, there is interest.

from spring-cloud-gateway.

@re6exp yes, PRs welcome

from spring-cloud-gateway.

i also want to rewrite request/response body, hold can pr to spring-cloud-gateway .
thanks

from spring-cloud-gateway.

@re6exp wow, that is major complex. I hope that is not what is ultimately needed. If it is, it will be a separate optional module.

from spring-cloud-gateway.

Hi All, Is Request Size limiting is available ?

from spring-cloud-gateway.

How about Set Response Content filter? I would love to see it on the list.

from spring-cloud-gateway.

@spencergibb @domainname
Here are some blocked changes that can be useful.

from spring-cloud-gateway.

Closing. Let's track filters individually now. Please open new issues.

from spring-cloud-gateway.