This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27550 - [imports]: Content-Disposition header should be recognized
Summary: [imports]: Content-Disposition header should be recognized
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20683
  Show dependency tree / graph
 
Reported: 2014-12-09 21:41 UTC by Morrita Hajime
Modified: 2014-12-10 22:14 UTC (History)
2 users (show)

See Also:

Attachments

Description Morrita Hajime 2014-12-09 21:41:58 UTC 
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.
Comment 1 Morrita Hajime 2014-12-09 21:43:11 UTC 
Originally reported here: https://crbug.com/439877