Offshoot from #345984: Client-side caching of administration menu:

Avoid separate AJAX requests for clients that don't have a cache (or disabled cache). (Failsafe measures)

Comments

sun’s picture

Title: Separate AJAX request in clients without client-side cache » Prevent separate AJAX request for clients without client-side cache
sun’s picture

Version: 6.x-3.x-dev » 7.x-3.x-dev
Category: task » feature
sun’s picture

Status: Active » Closed (cannot reproduce)

Actually, I never ran into this issue.

Fidelix’s picture

Status: Closed (cannot reproduce) » Active

I did.
I activated Devel memory consumption output, and I get it two times.

Then, I edited function _drupal_bootstrap_page_header(), and did a var_dump of $_SERVER.
This is the querystring:

["QUERY_STRING"]=> string(56) "q=/js/admin_menu/cache/2e48b65cabaf285c9887325703a5acf1&"

Elijah Lynn’s picture

Issue summary: View changes

I just went through this in #1897362: Admin_menu 'Cache menu in client-side browser' generates a second page request. and pressing F5 in a browser will cause a second cache validation request and the response will be a lightweight 304 Not Modified served from Drupal Cache. However, if you just press enter in the address bar then you will get a 200 OK (served from browser cache). Are you still experiencing this?

I am suspecting this isn't an issue anymore and this can be closed.

markhalliwell’s picture

Status: Active » Closed (duplicate)
Related issues: +#2219467: Fix client side caching

Closing as a likely duplicate of this related issue.