Closing this ticket.

Hi Jeremy,

Did it work for you?

Mashape do not cache anything so It might come from the origin server.

I found a workaround by adding a random number to a parameter that will be ignored by the backend like this: https://healthruwords.p.mashape.com/v1/quotes/?n=22

where
n is a parameter that will be ignored
and 22 is a random number

This bypasses all the caches. We are currently upgrading the platform and hopefully this workaround will not be necessary anymore soon enough.

Let me know if that works for you.

No, didn’t have that (X-Mashape-Version and X-Mashape-Proxy-Response) in the response header.

Do you receive this last header X-Mashape-Proxy-Response=true?

Headers sent as response

When consuming an API through Mashape, you will always receive the following headers appended to the response:

X-Mashape-Version
The current version of the proxy used by Mashape.

X-Mashape-Proxy-Response
Set to “true” when the response has beenentirelygenerated by Mashape and not by the API. You will see this header, for example, when the API is temporary down or when you use invalid Mashape credentials.

http://docs.mashape.com/headers#headers-request

thanks. 😃

Ok, hang on to your hat 😃 and we will get Mashape’s answer to this issue. I haven’t see a way to bypass their cache so far.

Hi, yes, did try curl on the terminal and also the rest-console plugin of chrome. still the return is not random.

Just a question meanwhile have you tried with cUrl on command line? Do you get the same result?

No worries. I believe there is a cache issue at Mashape.
Let me check with them and we get back to you.