Anderson, Colin D
My feedback
-
186 votes
Thanks for the feedback. This is something we would like to do. We will take a look.
corey
Anderson, Colin D
supported this idea
·
-
197 votes
Thank you for all the votes and feedback. We have started work on this and the capability will be supported soon. If you would like to get in touch with us to discuss your scenarios, please fill this form: https://aka.ms/ApplicationGatewayCohort
Anderson, Colin D
supported this idea
·
-
236 votes
Valid suggestion subject to customer upvote
Anderson, Colin D
supported this idea
·
-
231 votes
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
Anderson, Colin D
supported this idea
·
-
284 votes
valid suggestion subject to upvote
Anderson, Colin D
supported this idea
·
-
517 votes
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
Anderson, Colin D
supported this idea
·
-
530 votes
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
Anderson, Colin D
supported this idea
·
-
623 votesAnderson, Colin D
supported this idea
·
-
745 votes
This is on our long term roadmap.
Anderson, Colin D
supported this idea
·
-
1,229 votes
We are evaluating this feature ask. However, it is not on our immediate roadmap.
-Rohin KAnderson, Colin D
supported this idea
·
-
1,265 votes
URL rewrite for Application Gateway v2 is currently in public preview! With this, you can now rewrite URL path and query string parameters based on a condition. The condition will be on request or response parameters.
Also, you get the ability to choose the routing to a backend pool based on the original URL or the rewritten URL.
We’d love for you to try it out and let us know your valuable feedback. Learn more here – https://aka.ms/urlrewritepreview and https://aka.ms/urlrewriteconfiguration
Anderson, Colin D
supported this idea
·
-
1,602 votes
valid suggestion subject to upvote
Anderson, Colin D
supported this idea
·
-
1,674 votes
Thanks for all your feedback so far. This is something we are looking to address relatively soon. Please stay tuned.
Anderson, Colin D
supported this idea
·
-
214 votes
An error occurred while saving the comment Anderson, Colin D
supported this idea
·
-
80 votesAnderson, Colin D
supported this idea
·
-
42 votestriaged · 2 comments · Networking » Azure Front Door Service · Flag idea as inappropriate… · Admin →Anderson, Colin D
supported this idea
·
-
313 votes
Valid feedback. Open for customer upvotes
Anderson, Colin D
supported this idea
·
-
111 votes
We’re evaluating more compressed storage formats. Meanwhile, please consider using a client-side compression library for encoding fields/JSON fragments that are not used for querying.
Anderson, Colin D
supported this idea
·
An error occurred while saving the comment Anderson, Colin D
commented
TimescalleDB supports transparent compression, and it achieves fantastic savings, even on JSON data. Would love to see this added to CosmosDB too
-
276 votes
Thank you for all the votes. We need more feedback on your scenarios. If you would like to get in touch with us for a discussion, please fill this form: https://aka.ms/ApplicationGatewayCohort
Anderson, Colin D
supported this idea
·
-
14 votes
An error occurred while saving the comment Anderson, Colin D
commented
Would be great to get some comment from Azure team about this?
Anderson, Colin D
supported this idea
·
This has hit me too.
The 942440 (SQL Comment Sequence) and 942450 (SQL Hex Encoding) rules are *particularly* annoying, and the way they work seems to be ridiculously simplistic - just blanket matching *anything* containing "--" or a hex string, not taking context into account at all! I don't expect something so basic given the price of Azure's WAF solutions...
After adding about 20 exclusions, and seeing yet more in the logs requiring exclusions, I conceded and disabled these 2 silly rules :-/