# User more info - Cache results and render optimization

**URL:** <https://meta.discourse.org/t/user-more-info-cache-results-and-render-optimization/17578>\
**Category:** Feature\
**Created:** [14 Luglio 2014, 10:06pm UTC](https://meta.discourse.org/t/user-more-info-cache-results-and-render-optimization/17578 "2014-07-14T22:06:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Lid](https://avatars.discourse-cdn.com/v4/letter/l/2bfe46/32.png) [@Lid](https://meta.discourse.org/u/Lid)\
**Post date:** [15 Luglio 2014, 12:58am UTC](https://meta.discourse.org/t/user-more-info-cache-results-and-render-optimization/17578/4 "2014-07-15T00:58:01Z")

</div>

@elberet I guess there are not many interesting faces/people here, if you are not checking each and every avatar.  
the base use case that you can look at is if you check a person, you closed the info box quickly and then wanted to see it again. just for this it is worth having short term caching, it does not make sense to make an identical ajax call in 2-3 seconds difference.

@sam  
The user info box is a possible future optimization an it is just an example of the missing cache capability.  
I did bring up the point that it may not be possible to cache ajax request on meta ( possibly at all?) I am not sure how much caching is needed on ajax requests. but the user box is an example.

I couldn’t check my code on discourse without secure HTTP(s) to confirm if it is SSL that prevent caching on ajax requests. or may be another header in the response.

Do you know of a Discourse instance that allow http requests without redirect to https?, So I can test and satisfy my curiosity?

---

_[View the full topic](https://meta.discourse.org/t/user-more-info-cache-results-and-render-optimization/17578)._