Skip to content
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.

Sign up for GitHub

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

Jump to bottom

HTTP/2 support #2701

Closed
citizenrich opened this issue Feb 12, 2017 · 227 comments
Closed

HTTP/2 support #2701

citizenrich opened this issue Feb 12, 2017 · 227 comments
Assignees
@a85 @parthverma1
Labels
feature http2 + sse Initiative All feature requests that will be taken up as a new initiative Plugin product/runtime protocol

Comments

@citizenrich
Copy link

  1. Postman Version: 4.9.3
  2. App (Chrome app or Mac app): Mac
  3. OS details: 10.12.3
  4. Is the Interceptor on and enabled in the app: Yes
  5. Did you encounter this recently, or has this bug always been there: Always
  6. Expected behaviour: HTTP2
@sdnts sdnts added the feature label Feb 16, 2017
@bhavin177
Copy link

Checking in to see if this on the roadmap?

@sdnts
Copy link

sdnts commented Aug 25, 2017

@bhavin177 We haven't taken a look at this yet.
You can follow our roadmap here

@zabojad
Copy link

zabojad commented Aug 31, 2017

We cannot test the APNS Provider API with Postman due to the lack of HTTP/2 support...

@mrccnt
Copy link

mrccnt commented Sep 17, 2017

+1 We also need to check our own and some external HTTP/2 APIs

@ovictorpinto
Copy link

+1 me too

@exoquester
Copy link

+1 here as well !!!

@hkalex
Copy link

hkalex commented Dec 10, 2017

+1 here!!

@Cloudmersive
Copy link

+1

1 similar comment
@coddo
Copy link

coddo commented Feb 5, 2018

+1

@aat-antoine
Copy link

One year later, not even in the roadmap. saaaaad :)

@Stavanger75
Copy link

+1

11 similar comments
@Walkerks
Copy link

+1

@devrck
Copy link

devrck commented Mar 17, 2018

+1

@schnable
Copy link

+1

@KevinLeigh
Copy link

+1

@39Er
Copy link

39Er commented Apr 25, 2018

+1

@EfrainReyes
Copy link

+1

@rodmaz
Copy link

rodmaz commented May 4, 2018

+1

@arthurgeron
Copy link

+1

@jorge0136
Copy link

+1

@esiskind-chwy
Copy link

+1

@ghost
Copy link

ghost commented May 30, 2018

+1

@pregress
Copy link

pregress commented Jun 5, 2018

Any update when will this be supported? More and more companies and api's are migrating to http 2.0

@mrccnt
Copy link

mrccnt commented Jun 5, 2018

As far as I can see it still isnt on the roadmap yet... Not even long term...

@a85 a85 added the Plugin label Jun 16, 2018
@ajesh-n
Copy link

ajesh-n commented Aug 31, 2018

+1

1 similar comment
@Moncefmd
Copy link

Moncefmd commented Sep 4, 2018

+1

@frock81
Copy link

frock81 commented Nov 22, 2023

+1

@ti-bone
Copy link

ti-bone commented Dec 1, 2023

Any updates?

@AndersKANYE
Copy link

+1

2 similar comments
@JAOUARiadh
Copy link

+1

@snowknet
Copy link

+1

@ctigrisht
Copy link

why is such a feature still not implemented? a third of the web uses it...

@safic2
Copy link

safic2 commented Jan 26, 2024

+1

1 similar comment
@andrearima
Copy link

+1

@appurva21 appurva21 mentioned this issue Feb 13, 2024
Closed
1 task
@gauravn00b
Copy link

7 Years and counting. I guess there is no hope here? :(

@ddevsr
Copy link

ddevsr commented Feb 27, 2024

@abhijitkane @a85 Cant make any progress this feature?

@danic-wd danic-wd mentioned this issue Mar 7, 2024
Open
@RyanMorganti
Copy link

If the feature can't be monetized, why implement it?

@iannacone
Copy link

+1

6 similar comments
@dorgan
Copy link

dorgan commented Jun 7, 2024

+1

@anbeck77
Copy link

+1

@anhnmt
Copy link

anhnmt commented Jun 19, 2024

+1

@clevercodenl
Copy link

+1

@Leonardo-Ferreira
Copy link

+1

@dertin
Copy link

dertin commented Jul 14, 2024

+1

@DSchau DSchau mentioned this issue Aug 6, 2024
Closed
1 task
@parthverma1
Copy link

Very Soon 🤐
image

@parthverma1
Copy link

parthverma1 commented Aug 14, 2024 •
edited
Loading

We appreciate your patience and continued interest in HTTP/2 support for Postman. We want to assure you that we have been closely tracking this issue and understand its importance to our community.

That’s why we are excited to share that we have added HTTP/2 support with version 11.8 (Download Link). You can now send HTTP/2 requests. We’ve also added support for ALPN negotiation with the “Auto” option, which allows Postman to figure out the supported protocol version automatically.

641f0d5a-d9c9-4cb4-b419-4ed6c319e67f-ezgif com-optimize

However, at the moment, HTTP/2 support is not available when:

  • Sending insecure HTTP requests
  • Sending requests using proxies

You can read more about it on how to use HTTP/2 on our Learning Center doc.

With this launch, we will be closing this issue. We encourage users to open a new issue if you encounter any HTTP/2-specific bugs.

Additionally, we would love to interact with community members to understand your unique use cases around HTTP/2. If you're interested in sharing your needs or providing feedback, please comment on this issue or email us at api-client@postman.com, particularly if you are willing to jump on a call or share use cases that you feel are not fulfilled by Postman.

@parthverma1 parthverma1 self-assigned this Aug 14, 2024
@LadyE215
Copy link

Thank you

@Tommykl33
Copy link

What?I'm lost

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@a85 a85

@parthverma1 parthverma1

Labels
feature http2 + sse Initiative All feature requests that will be taken up as a new initiative Plugin product/runtime protocol
Projects
Runtime Triage and Development
Status: Ready
Milestone
No milestone
Development

No branches or pull requests