Přeložit "accept" do Angličtina

EN The most common example of this is Vary: Accept-Encoding, which will result in the browser caching the same object in different formats, based on the different Accept-Encoding request header values (i.e

• Vary
• Accept-Encoding
• caching the same
• different formats
• Accept-Encoding request header

EN Another common value is Vary: Accept-Encoding, User-Agent, which instructs the client to include both the Accept-Encoding and User-Agent values in the cache key

• Another common value
• Vary
• Accept-Encoding
• User-Agent
• instructs the client
• cache key

EN Accept-Encoding accounts for almost 92% of Vary?s use, with User-Agent at 10.7%, Origin (used for CORS processing) at 8%, and Accept at 4.1% making up much of the rest.

• Vary
• Origin
• used for CORS
• Accept at making

EN The default action for the three internal chains INPUT, FORWARD and OUTPUT is set to ACCEPT

• three internal chains
• FORWARD
• OUTPUT is set
• ACCEPT

EN The default action for the three internal chains INPUT, FORWARD and OUTPUT is set to ACCEPT

• three internal chains
• FORWARD
• OUTPUT is set
• ACCEPT

EN Click "Accept"below if you agree to the use of all cookies.

• Click

EN Click "Accept"below if you agree to the use of all cookies.

• Click

EN Fix: PHP error ?Uncaught Error: array_merge() does not accept unknown named parameters? when visiting the ?About? page using PHP 8+.

• Fix
• PHP error
• Uncaught Error
• does not accept
• named parameters
• page using PHP

EN The server responds with the object and indicates that the version it is sending should include the value of the Accept-Encoding request header.

• object
• sending should include
• request

EN However, when discussing shared proxies and CDNs, using values other than Accept-Encoding can be problematic as it dilutes or fragments the cache and can reduce the amount of traffic served from cache

• However
• discussing shared proxies
• CDNs
• fragments the cache
• reduce the amount

EN Doing so allows for proper storage in the cache for future requests, applying the correct Content Security Policy (CSP), and setting the correct Accept request headers.

• Doing so allows
• cache for future
• applying the correct
• Security Policy
• CSP
• setting the correct
• request

EN This site uses cookies to improve your user experience. By using this website, you agree that we can place cookies on your device. More info Accept

• site uses cookies
• improve your user
• website
• device
• info Accept