Zum Inhalt springen
View in the app

A better way to browse. Learn more.

Fachinformatiker.de

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Traffic und Browser Cache

Empfohlene Antworten

Veröffentlicht

hi all,

der broswer, wenn aktiviert, speichert ja eine menge dateien in seinem cache, bilder cookies usw. wie wirkt sich das auf den traffic eines servers aus. nehmen wir doch als beispiel das forum hier. ich verfolge so die threads die mich interessieren. ich denke mal die smilies usw. hat der browser dann in seinem cache. wie läuft das nun, wenn ich die seite neu anfordere? verringert der browser cache auch den traffic auf den server?

Original geschrieben von Art

verringert der browser cache auch den traffic auf den server?

Hallo,

klar, der Browser fragt dann an ob sich die Datei geändert hat. Falls nicht, bekommt der vom Webserver anstatt Status Code 200, Status Code 304 "not modified" zurück und lädt die Datei aus dem Cache.

--------------

10.3.5 304 Not Modified

If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.

The response MUST include the following header fields:

- Date, unless its omission is required by section 14.18.1

If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC 2068], section 14.19), caches will operate correctly.

- ETag and/or Content-Location, if the header would have been sent

in a 200 response to the same request

- Expires, Cache-Control, and/or Vary, if the field-value might

differ from that sent in any previous response for the same

variant

If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.

If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.

If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.

-----------------

Gruß Jaraz

wow. thx

Archiv

Dieses Thema wurde archiviert und kann nicht mehr beantwortet werden.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.