Loading Profile...
wish list
I use apigee to monitor my api's ... and love your service. These would be my wishlist
Error LOG:
If i could look at the error rate->api-> and then drill down to look at the actual error request and response that would be great.
Load balance:
This can avoid me the need to use an external load balance r for my apps.
Security :
Even a simple HTTP basic auth ... which will eliminate the need for implementing security at the application layer
Error LOG:
If i could look at the error rate->api-> and then drill down to look at the actual error request and response that would be great.
Load balance:
This can avoid me the need to use an external load balance r for my apps.
Security :
Even a simple HTTP basic auth ... which will eliminate the need for implementing security at the application layer
I’m excited
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?Rajan,
Thanks again for using Apigee and giving us the feedback.
Great requirements. I added them to our backlog. We're likely to tackle them in the following order:
1. error log
2. security
3. load balance
I’m thankful
-
Inappropriate?In extension to point 2: I think Basic Auth without SSL/HTTPS makes little sense. The lack of SSL support is (most unfortunately) a showstopper for me. I would very much love to see that!
I’m disappointed
-
Inappropriate?Thanks, Harm, for the feedback.
We've heard from other folks in the past few days about the importance of SSL. We're going to bump it up to the top of our backlog.
We'll share a design brief about how we plan to handle SSL certificates & HTTPS here on GetSatisfaction. It would be great to get your feedback once we do.
-b
I’m thankful
-
Inappropriate?Good to hear! I'll keep following this idea. Bring on the design brief!
I’m confident
-
Inappropriate?sweet. thanks, Harm.
-
Inappropriate?Can I add to number 2 :
Allow us to pass/hide some URL query string params , for example: I could hide some API key from my App users
I’m excited
1 Comment
Add a comment
This is one of the best points
-
Hi Mike, how should we understand the hiding? for example, have Apigee track the params, but strip out the content before it gets to the client? -
Inappropriate?@Brian,
To be more clear..
Target API should be queried like this:
http://api.site.com/?key=123&q=keywords
,where key is private information , and q is the search term.
So, I need to map this (not just a domain)
http://api.site.com/?key=123
to proxy like this:
http://site.apigee.com/
and requesting
http://site.apigee.com/?q=keyowrds
will return response from
http://api.site.com/?key=123&q=keywords
So, If I use the target API in JavaScript. source code will not reveal my API key.
I’m thankful
1 Comment Add a comment
This is one of the best points
-
Excellent description of the problem. I think I get it now.
Here's a solution proposal:
As part of setting up your proxy along with specifying api.site.com, Apigee would also allow you to specify any additional parameters that would be appended to the end of every API request. That way your API key would not be in your source code, but instead only specified as part of your Apigee proxy settings.
This is a great idea. We could also extend it to adding parameters in the header of any request. Thanks, Mike, for sharing that. I added it to our backlog. -
EMPLOYEE
