- From: <bugzilla@jessica.w3.org>
- Date: Tue, 09 Dec 2014 21:41:58 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27550
            Bug ID: 27550
           Summary: [imports]: Content-Disposition header should be
                    recognized
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: morrita@google.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 20683
The Content-Disposition HTTP header is handled in page navigation in HTML
so HTML Imports so far doesn't care about that.
As the header is sometimes used as a protection mechanism, it'd be better for
HTML Imports to see it, and probably just make it an error if there is
Content-Disposition header in the response. The concept isn't compatible
to HTML Imports anyway.
I feel this a bit too defensive, but we can start from conservative side.
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 9 December 2014 21:42:00 UTC