移动端Chrome分享URL异常：默认显示旧链接及.htaccess关联排查

Hey there, let's break down your questions one by one:

Yes, mobile Chrome does have mechanisms that can store data related to sharing—though it’s not exactly "caching the shared URL" in the traditional browser cache sense. Chrome often caches Open Graph (OG) metadata (like og:url, og:title, etc.) from pages you visit, since social sharing features rely heavily on this data to generate previews. This cached metadata can persist even after clearing basic browsing history, as it’s sometimes stored in a separate cache tied to social sharing or the browser’s link preview system.

Looking at your provided .htaccess code, it’s highly unlikely to be the direct cause of this issue. Here’s why each section doesn’t contribute to the problem:

• The mod_deflate block only compresses CSS, HTML, and PHP files to reduce load times—this has no impact on how social sharing metadata is stored or retrieved.
• The mod_expires section sets cache durations for static assets and HTML. While it configures a 1-month cache for HTML, clearing your Chrome browsing history should have wiped this cached content (browser cache clears include both expired and non-expired files). Even if some HTML was cached, the core issue here is a stuck sharing link, not outdated page content.
• The mod_rewrite rules are basic security measures to block malicious query strings—they don’t interfere with URL sharing or metadata handling.
• The PHP handler section simply sets your default PHP version, which has no bearing on this problem.

What’s actually causing the stuck sharing link? #

This issue is almost certainly tied to Chrome’s cached Open Graph metadata for your site. When you shared /contact via WhatsApp, Chrome fetched and stored the OG data (including the critical og:url tag) for that page. Later, when you attempt to share /home, Chrome may be pulling this cached metadata instead of re-fetching fresh data for the new page.

Recommended fixes to try: #

• Force a cache-bypassed reload: On mobile Chrome, navigate to /home, tap the three-dot menu, hold the "Reload" button until you see "Reload and bypass cache", then select that option. This will force Chrome to fetch fresh metadata for the page.
• Verify your site’s OG tags: Double-check that each page has unique og:url, og:title, and og:description tags. If /home incorrectly uses the same og:url value as /contact, that would cause sharing to default to the wrong link.
• Clear Chrome’s Site Data: Instead of just clearing browsing history, go to Chrome Settings > Privacy and security > Clear browsing data > Select "All time" > Check "Site data" and "Cached images and files" > Tap "Clear data". This targets more persistent cache stores that might hold the stuck OG metadata.
• Test in incognito mode: Open /home in an incognito tab and try sharing it. If this works correctly, it confirms the issue is isolated to cached data in your regular Chrome profile.

内容的提问来源于stack exchange，提问作者Lovelyn