Traducir "none" a Inglés

EN For first-party SameSite=lax is used by 50.06%, SameSite=strict by 2.03%, and SameSite=none by 47.96%, while for third-party SameSite=lax is used by 23.40%, SameSite=strict by 0.10%, and SameSite=none by 76.50%.

• first-party
• while for third-party

EN Learn how to get rid of the prompt “MTA-STS policy is missing: STSFetchResult.NONE ” by implementing and hosting the MTA-STS policy file correctly.

• implementing
• hosting the MTA-STS
• file

EN What is a DMARC Policy? | P=Reject | P=none

• DMARC Policy

EN Even organisations like UNICEF have yet to implement DMARC with their domains, and the White House and US Department of Defense both have a DMARC policy of p = none, which means they’re not being enforced.

• yet to implement
• domains
• White House
• Department of Defense
• none
• means
• being

EN Proactively assist them in their journey from p=none to p=reject, helping them achieve DMARC compliance

• helping them achieve
• compliance

EN none= Its purpose is to ask search engines not to index nor follow any link on that page: noindex and nofollow. It tells them not to react when they see the page.

• index nor follow
• noindex
• nofollow

EN Knowledge representation - Linked open data - Metadata - Recreational master of none - Ex-renovator - Coffee, a vinyl record and the newspaper

• Knowledge representation
• Metadata
• Ex-renovator
• Coffee
• vinyl record
• newspaper

EN These can be viewed here: https://privacy.google.com/businesses/compliance/#!?modal_active=none#gdpr

• businesses
• compliance

EN We recommend starting with p=none to ensure that your emails are not impacted.

EN With a none policy you can monitor your domain with DMARC (RUA) Aggregate Reports and keep a close eye on your inbound and outbound emails, this will help you respond to any unwanted delivery issues

• monitor your domain
• DMARC
• RUA
• Aggregate Reports
• keep a close
• inbound
• outbound emails
• delivery issues

EN This tag addresses the DMARC policy mode. You can select from reject, quarantine, and none. Learn more about

• policy mode
• select from reject
• quarantine
• none

EN If a subdomain has an explicit DMARC record, this record will take precedence over the DMARC policy for the parent domain, even if the subdomain uses the default setting of p=none

• DMARC record
• record will take
• parent domain
• uses the default

EN DMARC policy can be set to none, quarantine and reject, depending on the intensity of DMARC enforcement you need at your organization

• set to none
• quarantine
• reject
• organization

EN The none policy does not enforce any action on spoofed emails that are failing DMARC and without the RUA/RUF tags, you lack the visibility needed to find out who is sending emails on your behalf (legitimate and spoofing entities)

• none policy does
• enforce any action
• failing DMARC
• without the RUA
• RUF tags
• lack the visibility
• behalf
• legitimate
• spoofing entities

EN Without the information provided by PowerDMARC, it is practically impossible to move your policy from monitoring only (p=none) to an enforcement policy that will protect your domain against spoofing (p=reject)

• PowerDMARC
• policy from monitoring
• protect your domain
• spoofing

EN We recommend starting with p=none to ensure that your emails are not impacted.

EN Proactively assist them in their journey from p=none to p=reject, helping them achieve DMARC compliance

• helping them achieve
• compliance

EN What is a DMARC Policy? | P=Reject | P=none

• DMARC Policy

EN DMARC policy can be set to none, quarantine and reject, depending on the intensity of DMARC enforcement you need at your organization

• set to none
• quarantine
• reject
• organization

EN The none policy does not enforce any action on spoofed emails that are failing DMARC and without the RUA/RUF tags, you lack the visibility needed to find out who is sending emails on your behalf (legitimate and spoofing entities)

• none policy does
• enforce any action
• failing DMARC
• without the RUA
• RUF tags
• lack the visibility
• behalf
• legitimate
• spoofing entities

EN Without the information provided by PowerDMARC, it is practically impossible to move your policy from monitoring only (p=none) to an enforcement policy that will protect your domain against spoofing (p=reject)

• PowerDMARC
• policy from monitoring
• protect your domain
• spoofing

EN Knowledge representation - Linked open data - Metadata - Recreational master of none - Ex-renovator - Coffee, a vinyl record and the newspaper

• Knowledge representation
• Metadata
• Ex-renovator
• Coffee
• vinyl record
• newspaper

EN These can be viewed here: https://privacy.google.com/businesses/compliance/#!?modal_active=none#gdpr

• businesses
• compliance

EN You can turn off MTA-STS for your domain by either setting the policy mode to none, thereby specifying to MTAs that your domain doesn’t support the protocol, or by deleting your MTA-STS DNS TXT record. 

• turn off MTA-STS
• domain by either
• domain
• protocol
• deleting your MTA-STS
• TXT record

EN The none policy does not enforce any action on spoofed emails that are failing DMARC and without the RUA/RUF tags, you lack the visibility needed to find out who is sending emails on your behalf (legitimate and spoofing entities)

• none policy does
• enforce any action
• failing DMARC
• without the RUA
• RUF tags
• lack the visibility
• behalf
• legitimate
• spoofing entities

EN none= Its purpose is to ask search engines not to index nor follow any link on that page: noindex and nofollow. It tells them not to react when they see the page.

• index nor follow
• noindex
• nofollow

EN Bar chart showing 33% of desktop and mobile pages with video have preload of none, 36% of desktop and 27% of mobile pages with video have auto, 24% and 33% respectively have metadata, and 4% and 5% respectively do not have this set.

• Bar chart showing
• desktop
• preload of none
• auto
• respectively have metadata

EN The preload attribute indicates whether a video should be downloaded, and it can have three values: none, metadata, auto (note that if left empty, the auto value is assumed)

• preload attribute indicates
• three values
• none
• metadata
• auto
• empty

EN The attribute has three possible values: None, Lax, and Strict

• attribute has three
• values
• None
• Lax
• Strict

EN Cookies with SameSite=None will be sent in all cross-site requests, whereas cookies with the attribute set to Lax will only be sent in navigational requests, e.g

• requests
• sent in navigational

EN This is confirmed by looking more closely at the values set in the SameSite attribute: the majority of third-party cookies (76.5%) have the attribute value set to None

• confirmed by looking
• attribute
• majority of third-party
• attribute value set
• None

EN When it needs to request the object from the server again, it includes an additional request header, called If-None-Match, which has the value passed in the ETag response header in the initial response:

• needs to request
• again
• includes an additional
• header
• called If-None-Match
• ETag response header
• initial

EN When the server receives this request, it can check whether the object has changed by comparing the If-None-Match header value with the current version it has of the file.

• changed by comparing
• If-None-Match header value

EN Again, we see a pair of headers being used for this conditional request processing—the ETag response header and the If-None-Match request header.

• Again
• pair of headers
• request
• ETag response header
• If-None-Match request

EN 86.1% of the responses contained the same ETag value, passed in the If-None-Match header of the corresponding request

• ETag value
• request

EN 89.9% of the responses contained the same ETag value, passed in the If-None-Match header of the corresponding request

• ETag value
• request

EN 89.9% of the mobile responses (86.1% on desktop) contained the same ETag value, passed in the If-None-Match header of the corresponding request

• mobile responses
• desktop
• contained the same
• value
• request