Skip to content

HttpHeaders should be a Map, or at least support enumeration of headers #2785

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jmesserly opened this issue Apr 28, 2012 · 3 comments
Closed
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-duplicate Closed in favor of an existing report library-io

Comments

@jmesserly
Copy link

From Eric J Smith:
Unable to iterate headers. I should be able to iterate the header names and values and get count. Why doesn't HttpHeaders derive from Map?

https://groups.google.com/a/dartlang.org/forum/#!topic/misc/6GBKm5fOrqA

@jmesserly
Copy link
Author

BTW, I noticed that _HttpHeaders actually does have a map internally:

class _HttpHeaders implements HttpHeaders {
  _HttpHeaders() : _headers = new Map<String, List<String>>();
 ...

@jmesserly
Copy link
Author

Added Duplicate label.
Marked as being merged into #2045.

@kevmoo
Copy link
Member

kevmoo commented May 14, 2014

Removed Area-IO label.
Added Area-Library, Library-IO labels.

@jmesserly jmesserly added Type-Defect area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. library-io closed-duplicate Closed in favor of an existing report labels May 14, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-duplicate Closed in favor of an existing report library-io
Projects
None yet
Development

No branches or pull requests

2 participants