• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Task
    • Report CloudFlare @supports Issue to Cloudflare Devs

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: Report CloudFlare @supports Issue to Cloudflare Devs

    • Issue Tools
      • View Changes
    1. issueid=4442 November 10, 2015 8:45 AM
      pegasus pegasus is offline
      VaultWiki Team
      Report CloudFlare @supports Issue to Cloudflare Devs

      Sent the following to Cloudflare support today:
      Hi,

      I am not a CloudFlare customer myself, but I represent a web application that has clients who are CloudFlare customers. Every such client/CloudFlare-customer that we have had has needed to disable CloudFlare caching of our application's CSS files, which requires using 2 rules (I understand only 3 rules are allowed in a free tier).

      When CSS contains an @supports block, e.g.
      @supports (display: flex) { .myClass { display: flex }}

      It works on the first request (cache miss), which means that the application is working properly and the CSS is fully present. However, once CloudFlare caches CSS, we consistently see that the cache hit cuts like so:
      @supports (display: flex) { .myClass { display: flex

      If anything appeared later in the original CSS file, it is missing in the cache response.

      This is an even worse problem if the CSS is embedded inline (which I think mod_cloudflare might do automatically for some files), because CloudFlare cuts the entire HTTP response in the same way for inline CSS.

      I am not sure if this problem extends to other CSS @ blocks, like @media, but you should ensure that it does not cause such a devastating condition as it currently does. Web sites affected by this issue either appear unstyled, or do not appear at all, when serving from the Cloudflare cache.

      Please resolve this and push it out to your customers ASAP.

      Thanks,
      Ted Phillips
      VaultWiki Team
    Issue Details
    Issue Number 4442
    Issue Type Task
    Project VaultWiki 4.x Series
    Category Styling / CSS
    Status Completed
    Priority 2 - Fatal / Database Errors
    Target Version Unknown
    Resolved Version (none)
    Milestone (none)
    Software DependencyAny
    License TypePaid
    Votes to perform 0
    Votes not to perform 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. August 16, 2016 7:08 PM
      pegasus pegasus is offline
      VaultWiki Team
      For reference:
      https://support.cloudflare.com/hc/en-us/requests/647716
      https://support.cloudflare.com/hc/en-us/requests/873790

      According to the ticket headers, the issue was "Solved"
      Reply Reply
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 6:18 AM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.