Notifications portlet makes pages cache useless

• Type: Bug
• Status: Verified
• Resolution: Unresolved
• Affects Version/s: 6.2.X EE
• Fix Version/s: None
• Component/s: Collaboration, Collaboration > API > Notifications
• Labels:
  • 6.2.x-only
  • QA-B
• Fix Priority: 3
• Liferay Contributor's Agreement:
  Accept
• Git Pull Request: https://github.com/sergiosanchez/liferay-plugins/pull/2

Steps to reproduce:

1. In Firefox, startup 6.2.x version and open firebug, Network tab.
2. Open default Liferay page. Be sure to NOT be logged in.
3. Check the http status code for /home HTTP GET request. It should be 200.
4. Refresh same page with F5. Now you should see that request returns HTTP 304 status (not modified).
5. Now deploy notifications-portlet.
6. Refresh page. As we deployed portlet we should see HTTP status 200 again.
7. Refresh page again. Check now the http status code for /home HTTP GET request.

Expected behavior: as page is cached and we already made a request, it should return HTTP 304 status.
Actual behavior: it returns HTTP 200, making it NOT cached in browser and hence causing network latency as it should get resources again.