# Toward swift-http-types 1.0

**URL:** <https://forums.swift.org/t/toward-swift-http-types-1-0/66632>\
**Category:** Development\
**Tags:** http\
**Created:** [August 7, 2023, 5:30pm UTC](https://forums.swift.org/t/toward-swift-http-types-1-0/66632 "2023-08-07T17:30:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guoye](https://avatars.discourse-cdn.com/v4/letter/g/c77e96/32.png) [@Guoye](https://forums.swift.org/u/Guoye)\
**Post date:** [August 7, 2023, 5:30pm UTC](https://forums.swift.org/t/toward-swift-http-types-1-0/66632/1 "2023-08-07T17:30:14Z")

</div>

Last month, swift-http-types 0.1.0 became open source and we received a lot of great feedbacks from the community. We hope to take the next step to deliver a stable release in September.

Currently, this is the list of outstanding issues that we plan to resolve before 1.0:

- Should order matter when comparing HTTPFields for equality? [#6](https://github.com/apple/swift-http-types/issues/6)
- More consistent naming for HTTPFields subscripts [#9](https://github.com/apple/swift-http-types/issues/9)
- Missing built-in field names [#12](https://github.com/apple/swift-http-types/issues/12)
- Support Codable [#13](https://github.com/apple/swift-http-types/issues/13)

Please let us know what you think by replying below or filing new issues: [Issues · apple/swift-http-types · GitHub](https://github.com/apple/swift-http-types/issues)