unexpected xhl ml error TypeError: NetworkError when attempting to fetch resource. v65e1559192.category.js:1:1924464
Content-Security-Policy warnings 2
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. 2
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/xh-desktop/js/v0c0d6631d0.runtime.js v0c0d6631d0.runtime.js
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/xh-shared/js/locales/va6847436df.en.js va6847436df.en.js
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/xh-desktop/v4d187d817f.manifest.js v4d187d817f.manifest.js
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/xh-desktop/js/v65e1559192.category.js v65e1559192.category.js
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-lvlt.xhcdn.com/xh-images/components/header/components/header-nav/flirtify.svg flirtify.svg
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://lcdn.tsyndicate.com/sdk/v1/interstitial.ts.css interstitial.ts.css
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://lcdn.tsyndicate.com/sdk/v1/interstitial.ts.js interstitial.ts.js
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/js/v2d698b88dd.track.min.js v2d698b88dd.track.min.js
Some cookies are misusing the recommended “SameSite“ attribute 3
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static-ah.xhcdn.com/js/v2d698b88dd.track.min.js. (Reason: CORS request did not succeed). Status code: (null).

Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/xh-desktop/fonts/va35c60c17b.xh-icons.woff2 2:63:14
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://lcdn.tsyndicate.com/sdk/v1/master.spot.js 2:151:865
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static-ah.xhcdn.com/xh-desktop/fonts/va35c60c17b.xh-icons.woff2. (Reason: CORS request did not succeed). Status code: (null).

downloadable font: download failed (font-family: “xh-icons” style:normal weight:400 stretch:100 src index:0): bad URI or cross-site access not allowed source: https://static-ah.xhcdn.com/xh-desktop/fonts/va35c60c17b.xh-icons.woff2
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/xh-desktop/fonts/v6b324555e8.xh-icons.woff v6b324555e8.xh-icons.woff
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://lcdn.tsyndicate.com/sdk/v1/interstitial.ts.css interstitial.ts.css
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://lcdn.tsyndicate.com/sdk/v1/interstitial.ts.js interstitial.ts.js
Loading failed for the <script> with source “https://lcdn.tsyndicate.com/sdk/v1/master.spot.js”. 2:1:1
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static-ah.xhcdn.com/xh-desktop/fonts/v6b324555e8.xh-icons.woff. (Reason: CORS request did not succeed). Status code: (null).

downloadable font: download failed (font-family: “xh-icons” style:normal weight:400 stretch:100 src index:1): bad URI or cross-site access not allowed source: https://static-ah.xhcdn.com/xh-desktop/fonts/v6b324555e8.xh-icons.woff
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/xh-desktop/fonts/v2f4cadb720.xh-icons.ttf v2f4cadb720.xh-icons.ttf
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://vrmedia-lm.xhcdn.com/promo/message/1485/65d344e633256.jpg 65d344e633256.jpg
Loading failed for the <script> with source “https://lcdn.tsyndicate.com/sdk/v1/interstitial.ts.js”. 2:2491:93
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static-ah.xhcdn.com/xh-desktop/fonts/v2f4cadb720.xh-icons.ttf. (Reason: CORS request did not succeed). Status code: (null).

downloadable font: download failed (font-family: “xh-icons” style:normal weight:400 stretch:100 src index:2): bad URI or cross-site access not allowed source: https://static-ah.xhcdn.com/xh-desktop/fonts/v2f4cadb720.xh-icons.ttf
downloadable font: no supported format found (font-family: “xh-icons” style:normal weight:400 stretch:100 src index:4) source: (end of source list)
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-ah.xhcdn.com/js/v2d698b88dd.track.min.js v2d698b88dd.track.min.js
Uncaught (in promise) DOMException: A network error occurred.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static-ah.xhcdn.com/js/v2d698b88dd.track.min.js. (Reason: CORS request did not succeed). Status code: (null).

<script> source URI is not allowed in this document: “https://static-ah.xhcdn.com/js/v2d698b88dd.track.min.js”. 2:2604:124
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static-ah.xhcdn.com/xh-desktop/fonts/9cf2e.xh-icons.woff2. (Reason: CORS request did not succeed). Status code: (null).

downloadable font: download failed (font-family: “xh-icons” style:normal weight:400 stretch:100 src index:0): bad URI or cross-site access not allowed source: https://static-ah.xhcdn.com/xh-desktop/fonts/9cf2e.xh-icons.woff2
Uncaught ReferenceError: Track is not defined
<anonymous> https://xhamster.com/tags/gum/2:2604
2:2604:146
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-lvlt.xhcdn.com/xh-desktop/js/async-5be305149ce0a073721e9be8513c1781470c8b7d8196612bf1689e38d1cff96b-3501.js v0c0d6631d0.runtime.js:1:4235
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://4lke.online/api/request/v1/tag_1?language=en&spotPageType=categoryPage&spotType=widgetMiddleLine&locationCountry=de&webp=1&sort=rated&date=alltime&orientation=straight&page=2&tag=Gum&tagId=99719&statsUID=65da0796c65504.87099740e1e&exp={“15”%3A{“g”%3A"b"%2C"v"%3A39}%2C"68"%3A{“g”%3A"b"%2C"v"%3A2}%2C"2602"%3A{“g”%3A"a"%2C"v"%3A1}%2C"7013"%3A{“g”%3A"a"%2C"v"%3A15}%2C"8009"%3A{“g”%3A"b"%2C"v"%3A3}}&thumbSize=mmsmall v65e1559192.category.js:1:1912006
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static-ah.xhcdn.com/xh-desktop/fonts/dccf7.xh-icons.woff. (Reason: CORS request did not succeed). Status code: (null).

downloadable font: download failed (font-family: “xh-icons” style:normal weight:400 stretch:100 src index:1): bad URI or cross-site access not allowed source: https://static-ah.xhcdn.com/xh-desktop/fonts/dccf7.xh-icons.woff
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://4lke.online/api/request/v1/tag_1?language=en&spotPageType=categoryPage&spotType=widgetMiddleLine&locationCountry=de&webp=1&sort=rated&date=alltime&orientation=straight&page=2&tag=Gum&tagId=99719&statsUID=65da0796c65504.87099740e1e&exp={“15”%3A{“g”%3A"b"%2C"v"%3A39}%2C"68"%3A{“g”%3A"b"%2C"v"%3A2}%2C"2602"%3A{“g”%3A"a"%2C"v"%3A1}%2C"7013"%3A{“g”%3A"a"%2C"v"%3A15}%2C"8009"%3A{“g”%3A"b"%2C"v"%3A3}}&thumbSize=mmsmall. (Reason: CORS request did not succeed). Status code: (null).

Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://www.googletagmanager.com/gtm.js?id=GTM-TLDPV3J v65e1559192.category.js:1:2215773
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-lvlt.xhcdn.com/xh-desktop/js/async-2ee1d1cbaf5a20079566c6c92401c8902379b844e8fd913f184145c545577150-3499.js v0c0d6631d0.runtime.js:1:4235
Referrer Policy: Ignoring the less restricted referrer policy “unsafe-url” for the cross-site request: https://static-lvlt.xhcdn.com/xh-desktop/js/async-932be89debc2915d0ee7d1f79fff4528e42d24cf8d6a2324d0e6f3274ca9ff42-3503.js v0c0d6631d0.runtime.js:1:4235
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static-ah.xhcdn.com/xh-desktop/fonts/fc264.xh-icons.ttf. (Reason: CORS request did not succeed). Status code: (null).

downloadable font: download failed (font-family: “xh-icons” style:normal weight:400 stretch:100 src index:2): bad URI or cross-site access not allowed source: https://static-ah.xhcdn.com/xh-desktop/fonts/fc264.xh-icons.ttf
downloadable font: no supported format found (font-family: “xh-icons” style:normal weight:400 stretch:100 src index:5) source: (end of source list)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://collector.xhamster.com/?log=stats-beta&stats_tkn=3%3A3%3A1708788861%3Ac80d60c7208b8eef1ee74f9e10861de798bf7d47. (Reason: CORS request did not succeed). Status code: (null).

TypeError: NetworkError when attempting to fetch resource. v65e1559192.category.js:1:2162424
The errors you’ve shared suggest that there are several issues happening with a webpage you are accessing. To help you better understand them, I’ll break them down into categories:

1. Content Security Policy (CSP) and Referrer Policy Warnings:
- The page is trying to use outdated or non-standard CSS properties like zoom. Modern CSS alternatives like transform should be used instead.
- The referrer policy of some requests is less restricted (unsafe-url) and is ignored. It’s a warning that a more secure referrer policy could be in place.

2. Cross-Origin Resource Sharing (CORS) Errors:
- There are multiple CORS errors. This means that resources loaded from different origins (domains) are being blocked due to browser security policies. To resolve this, the server hosting the external resources needs to include appropriate CORS headers that allow these resources to be loaded by the page.

3. Font Loading Issues:
- The page has several errors relating to font loading. It seems that web fonts are being blocked due to CORS restrictions or incorrect paths. Hosting the fonts correctly and setting CORS headers could resolve these problems.

4. Cookie Warnings:
- Some set cookies do not have a correct SameSite attribute, which could lead to warning messages. The SameSite attribute is important for controlling how cookies are shared with different sites (e.g. for third-party contexts).

5. JavaScript Errors:
- The errors show that there are undefined references (e.g., Track is not defined) and failures loading JavaScript files, causing functionality issues on the page. These could be due to mistyped URLs, incorrect paths, or CORS issues as well.

6. Network Errors:
- You have a TypeError related to a network error when fetching a resource. This could mean there’s a problem with the connection to the server or that the server is not responding correctly to the fetch request.

7. General Observations:
- It appears that the errors are coming from a website that possibly hosts media content, possibly adult content, as indicated by the domain names and URLs in the errors.

To resolve these issues, the web developer(s) of the page would need to:

- Correctly set CSP and Referrer Policy headers to balance security and functionality.
- Ensure that CORS headers are set up properly on the server side for external resources.
- Host font files correctly and set up CORS headers for them if they are to be accessed from external domains.
- Audit and correct JavaScript files to ensure they are being loaded properly and that all references are defined.
- Review and set cookie attributes correctly to comply with best practices.
- Check the network to ensure there’s a reliable connection to the servers hosting the resources.

If you are a user encountering these issues on a website you do not control, there is little you can do besides reporting the issues to the website’s support team. If you are a web developer, you’ll need to address these issues in your code and server configuration.
this site works weird, it looks as it using all possible caching mechanisms in firefox browser. some of it in "_cfg:“882643c0ea2ddda2c343330c87fa3f61"” etc.
It sounds like you’re describing symptoms of aggressive caching strategies employed by the website you’re visiting. Caching is a common technique to improve loading times and reduce server load by storing copies of files locally in the user’s web browser. Whenever the browser requests the same file again, it can retrieve it from the cache rather than downloading it from the server.

Aggressive caching can involve multiple layers and strategies, such as:

1. Browser caching: Instructing the browser to store files like stylesheets, scripts, and images locally for a set period.

2. Service Workers: JavaScript workers that the site registers. They can intercept network requests, cache or retrieve resources from the cache, serve offline content, and even perform updates in the background.

3. LocalStorage and IndexedDB: Web storage solutions for storing data like settings, user preferences, or even offline data for web apps.

4. ETags and validation tokens: Mechanisms that servers use to validate cached resources, which avoids re-downloading if the content hasn’t changed.

5. URL fingerprinting: Technique where URLs of assets like JavaScript/CSS files have a unique fingerprint (often a hash or version number in the filename/path) which changes every time the file changes. It ensures that users always get the most up-to-date version of the file due to the new, unique URL.

6. CDN caching: Content delivery networks cache content at multiple points of presence globally to serve users from the nearest location, thus reducing latency.

If a website seems to be storing configurations with hashes like the one you described ("_cfg:"882643c0ea2ddda2c343330c87fa3f61"), it’s likely using some form of fingerprinting or versioning for its cached assets. The alphanumeric string appears to be a hash that changes when the configuration or the content of the files change. By changing this hash, the website can update the content on the user’s side without having to clear the browser’s cache manually since the new hash will make the browser treat it as a completely different file.

While caching provides many performance benefits, overuse can sometimes cause issues when a site needs to update content or when things go wrong, which could lead to the kind of weird behavior you’re experiencing. Clearing your browser’s cache might temporarily fix issues, but for longer-term solutions, the site’s developers may need to optimize their caching strategies or have logic in place to handle cache invalidation when updates occur. If you continue experiencing problems, reaching out to the website’s support team with specific details may also help them address any underlying issues.
no, I’m using tor browser which supposedly shouldn’t store that chache. this site using tons of cookies for tracking things and user id and etc. when you trying to delete all cookies and session ones through dev tools, some chache still left there in browser, and only delete all history through browser settings helps to get rid of all chache and cookies from this site. any ideas?
The Tor Browser is designed for enhanced privacy and anonymity and utilizes the Firefox browser as its base. It has various features that make it less susceptible to tracking, such as disabling third-party cookies by default, using HTTPS whenever possible, and clearing cookies when the browser is closed. However, some persistent mechanisms may still allow websites to store data on your system or maintain your session across different browsing periods.

Here’s what might be happening:

1. HTTP Strict Transport Security (HSTS) Supercookies:
Websites can store identifiers in the browser’s HSTS cache, which isn’t cleared with regular cookies and cache. Tor Browser, however, periodically clears its HSTS state, but some persistence could occur between those clears.

2. Service Workers:
Service Workers, which can cache resources for offline use, may be active. These are not cleared when you clear cookies but should be cleared when clearing the entire browsing history.

3. LocalStorage & IndexedDB:
Data stored in LocalStorage or IndexedDB is website-specific data storage. This data is not removed when cookies are cleared; it usually requires clearing the complete browsing data from the browser’s settings.

4. Persistent Cookies in Extensions/Add-Ons:
If you have any extensions or add-ons installed that are not included with the Tor Browser by default, they could potentially store cookies or data.

5. Browser Fingerprinting:
While not a form of caching, browser fingerprinting can allow a website to recognize you based on your browser’s unique characteristics. The Tor Browser includes various protections against fingerprinting, but it’s an ongoing battle.

6. Session Restore:
Firefox-based browsers, including Tor Browser, have a session restore feature that may save the session’s state, potentially across restarts if not configured properly.

7. First-Party Isolation:
Tor Browser includes a feature called First-Party Isolation, which prevents cross-site tracking by ensuring that all browser identifiers are scoped to the URL’s domain you are currently visiting. But if not interacted with correctly, this might cause confusion when attempting to clear site-specific data.

To ensure that all traces are removed:

- Always close Tor Browser when finished with a session, as this should clear all cookies and potentially unload any service workers.
- Clear all browsing history, including offline data and cached web content. You can find this option under “Privacy & Security” in the Tor Browser settings.
- Do not install any additional extensions or add-ons, as they could interfere with the privacy features of Tor Browser.
- Keep your Tor Browser updated to ensure you have the latest privacy protections.

If you want to guarantee no persistent data storage, consider using the Tor Browser on a bootable live USB operating system, such as Tails. Tails is designed to leave no trace on the machine after shutdown.
you are generating uninformative bullshit, because tor browser has Service Workers disabled.
Apologies for the confusion. You’re right that the Tor Browser has Service Workers disabled to prevent potential privacy issues.

In the context of Tor Browser, which is designed to not store persistent information, there are still a few other reasons why you might experience persistent behavior or “leftover” cache after you think you’ve cleared all cookies and session data:

1. Tor State Directory: Tor Browser keeps a state directory which contains information about the Tor client’s state. This is used to maintain some degree of persistency between sessions, and although it shouldn’t contain any personal browsing information, it can maintain certain Tor-related settings.

2. NoScript & HTTPS Everywhere Data: Tor Browser comes with additional extensions like NoScript and HTTPS Everywhere. These extensions have their own settings and data which may not be immediately cleared when you remove cookies and cache through the browser.

3. Profile Folder: Firefox-based browsers, including Tor Browser, store user data in a profile folder. While Tor Browser is meant to not keep any personal data after closing, there could be scenarios where some data is not deleted as expected.

4. Disk Cache: Even though Tor Browser tries to keep as much as it can in memory, there’s a possibility that the disk cache is not entirely cleared. This could happen due to unexpected shutdowns or software bugs.

To clear all possible caches and data in Tor Browser:

- Use the “New Identity” feature: Click on the hamburger menu (≡) in the top right corner, then click on “New Identity”. This will close all tabs and windows, clear all private information such as cookies and browsing history, and use a new Tor circuit for all connections.

- Delete the Tor Browser Folder: If you want to completely reset the Tor Browser, you can close the browser and manually delete the Tor Browser’s directory from your file system and then reinstall it.

- For an even stronger guarantee against persistent data storage, as mentioned in the previous response, consider using a live operating system like Tails which is designed to leave no trace after the session ends.

If you are still experiencing issues, it might be worth checking any recent changes to the Tor Browser that could affect data storage, or even reporting an issue to the Tor Project, as this behavior could potentially be a bug or regression.
is there any hard reset in tor browser to turn it all to factory defaults?
Tor Browser does not have a built-in “hard reset” feature that restores it to factory defaults with a single click. However, you can manually achieve a complete reset by deleting the Tor Browser and its associated data, and then downloading and re-installing it. Here’s how to do that:

### For Windows:

1. Close Tor Browser if it’s running.
2. Go to the folder where the Tor Browser is installed (usually it’s on your Desktop or in your Downloads folder).
3. Delete the Tor Browser folder.
4. Empty your Recycle Bin to ensure the files are completely removed.
5. Download the latest version of Tor Browser from the official source: https://www.torproject.org/download/
6. Install Tor Browser by running the downloaded file.

### For macOS:

1. Close Tor Browser if it’s running.
2. Open the Applications folder.
3. Drag the Tor Browser application to the Trash.
4. Empty the Trash to clear the files from your system.
5. Download the latest version of Tor Browser from the official source: https://www.torproject.org/download/
6. Open the downloaded .dmg file and drag the Tor Browser application into your Applications folder.

### For Linux:

1. Close Tor Browser if it’s running.
2. Delete the tor-browser_en-US (or the respective localized folder) in your home directory or wherever you extracted it.
3. Empty the Trash or delete the files from the command line to ensure they are removed.
4. Download the latest version of Tor Browser from the official source: https://www.torproject.org/download/
5. Extract the downloaded file and start the Tor Browser.

Please note that you might want to back up bookmarks or any necessary data before doing this, as this process will remove all Tor Browser data from your system. Additionally, you might want to consider using a system cleaner to remove any residual files that might not have been deleted during the manual process, although in most cases, deleting the browser folder should suffice for a complete reset.
“Tor Browser does not have a built-in “hard reset” feature that restores it to factory defaults”. then let’s build it in linex, because your reinstalling methods is lame.