Currently if I scan(from both UI and CLI) using ZAProxy it sends HTTPS Traffic using HTTP1.1 version, Do we have any Support or Workaround to send HTTPS Traffic using HTTP2.0 version in ZAProxy.
Any help on this is much appreciated
No ZAProxy does not support HTTP/2 at this time.
The Paros networking layer used by ZAP is old, and lacks support of modern options such as HTTP/2. They planned to replace this but there is no ETA as of now.
refer the thread : https://github.com/zaproxy/zaproxy/issues/1765
Related
I'm a newbie developer. I wanna know, Do i need grpc-web library even if the browser supports HTTP2 ?. If the answer is yes, please tell me why
Thanks in advance
According to this grpc.io blog post, as of 2019 browsers did not support fine-grained control of HTTP2 requests needed to implement direct gRPC connection from javascript.
For this reason a separate library and proxy, such as implemented by gRPC-Web, is needed.
Looks like Google App Engine didn't support it yet as of early 2015. Does Heroku support it? Wondering what does it take, shouldn't it work if we deploy all appropriate dependency and use the right port? (assuming authentication will be taken care of)
No, Heroku doesn't support HTTP/2 required for gRPC to work.
HTTP/2 is not currently supported on Heroku although this may change in future. You can find out about our currently supported HTTP protocols here: https://devcenter.heroku.com/articles/http-routing#http-versions-supported
Heroku only accepts incoming requests on Port 80 and Port 443. That'll probably be the limiting factor.
I am trying to find out if Ibm ISAM/Webseal supports the websocket protocol. I've tried to google for it, but with no success. Does anyone of you know if it does and if it needs any configuration to support it?
ISAM 9.0.2.0 supports the WebSocket protocol. ISAM 9.0.2.0 should be released in November 2016.
ISAM will happily take and deal with most packets that are HTTP formatted. WebSockets however are not supported.
When I connect to signalR hosted in same virtual directory, I get data via websocket transport. But in case of cross domain, long polling is getting used as a transport.
Here browser compatibility is not an issue as I am trying in Chrome browser.
What I can do to use websocket as a transport in case of cross domain.
I have tried every possible solution available on net, including available at signalR wiki.
https://github.com/SignalR/SignalR/wiki/SignalR-JS-Client-Hubs
Thanks David for answering my question in the comments:
Because only IIS8 supports websockets and neither SSE or ForeverFrame works cross domain so you're stuck with long polling –
I was doing AJAX implementation and would like to use Websocket when the client web browser supports it. Is there any frameworks that supports Websocket but falls-back to other methods when it detects the client side doesn't support Websocket.
There is also Atmosphere
http://atmosphere.dev.java.net
which support both client and server.
Yes sort of see www.kaazing.org
Kaazing Gateway supports all major browsers (Firefox version 1.5 and higher, Internet Explorer version 5.5 and higher, Safari version 3.0 and higher, Opera version 9.5 and higher, and Google Chrome version 0.2 and higher).
Socket.io is designed for this.
http://socket.io/
It is purely javascript that tries several different transport methods including XHR long-polling, WebSocket and FlashSocket amongst others.
You could also use Nirvana from www.my-channels.com.
When WebSocket is not supported it will fall back to a Comet based approach transparently.
Of course, you could try using jWebSocket, it is a pure Java/JavaScript high speed bidirectional communication solution for the Web - secure, reliable and fast. jWebSocket is provided to you to create innovative HTML5 based streaming and communication applications on the web. HTML5 WebSockets will replace the existing XHR approaches as well as Comet services by a new flexible and ultra high speed bidirectional TCP socket communication technology. jWebSocket is an open source Java and JavaScript implementation of the HTML5 WebSocket protocol with a huge set of extensions. Some demos or examples can be seen for you in the website, you can visit it here: https://jwebsocket.org/