Home → Support →

JSON Response Caching

• Edit

inderpal

21 Apr, 2011 12:44 AM

I've been banging my head against the wall for a while now trying to figure out what is wrong or what I'm doing wrong. I've created a controller to be called from a POST called 'APILogOn'. The user credentials are entered and it sends back a JSON response like so...
strResult = "{info:\"User is valid\",status:\"success\"}";
or
strResult = "{info:\"User is not valid\",status:\"fail\"}";

Now, that works... Yay! However, when I go to change the JSON result to something else, it still returns the original json data. In fact, I've uncommented out the controller 'APILogOn' and it still returns valid data. I'm using curl to test this.

I've made some other modifications to my application to make sure that it was being pushed to the apphb.com servers correctly and it is. Any help would be greatly appreciated.

Thanks!

1. Support Staff 1 Posted by friism on 21 Apr, 2011 01:09 AM

   

   This is unlikely to be an AppHarbor issue. We never cache content (other than the caching you manage yourself with OutputCache etc.) and POST's, in particular, are never cached.

   Let us know if you figure out what the problem is.

   • Edit

2. friism closed this discussion on 21 Apr, 2011 01:09 AM.

3. inderpal re-opened this discussion on 21 Apr, 2011 07:27 PM

4. 2 Posted by inderpal on 21 Apr, 2011 07:27 PM

   

   I'm an idiot. I swear I clean and rebuilt the solution, but I didn't. The changes that I made to test that the release worked were only HTML changes (which obviously don't need to be rebuilt). Thanks for your help though. A few questions not related to this... Where is appharbor hosted? Can it handle a load of a lot of users? If not, is there something that a user can do/change to accommodate that or should I moved to a rackspace or some other dedicated solution?

   Thanks!

   • Edit

5. Support Staff 3 Posted by friism on 21 Apr, 2011 08:18 PM

   

   Glad you got it working! Are you building locally and pushing compiled dlls? The recommended route is to leave generated website dll's out of the repository and let AppHarbor build them. This will avoid issues like you experienced.

   AppHarbor is hosted on Amazon EC2 and is built to scale to very high loads. Scaling to multiple web instances is not currently exposed to developers, but will be soon. The main AppHarbor site already runs on multiple instances and we are hosting several other high-traffic sites. We expect to publish a case-studie soon.

   Let us know if you have more questions.

   • Edit

6. friism closed this discussion on 21 Apr, 2011 08:18 PM.