Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / sunng87/ring-jetty9-adapter issues and pull requests

#144 - Pass correct arity of params to `ws/upgrade-websocket`

Pull Request - State: closed - Opened by alexandergunnarson 3 months ago - 1 comment

#143 - feat: jetty 12.0.15

Pull Request - State: closed - Opened by sunng87 3 months ago

#142 - Unix domain socks support

Issue - State: open - Opened by sunng87 4 months ago

#141 - feat: update ring to 1.13

Pull Request - State: closed - Opened by sunng87 4 months ago

#140 - refactor: make http2 module optional

Pull Request - State: closed - Opened by sunng87 5 months ago

#139 - fix: return true with async handler

Pull Request - State: closed - Opened by sunng87 6 months ago

#138 - Async option causes a non-fatal error

Issue - State: closed - Opened by robinlahtinen 6 months ago - 1 comment

#137 - feat: support http2 request headers that contains multiple cookie fields

Pull Request - State: closed - Opened by rmrt1n 8 months ago - 1 comment

#136 - HTTP/2 Cookies are unintentionally truncated/removed

Issue - State: closed - Opened by rmrt1n 8 months ago - 3 comments

#135 - fix: correct check for websocket ping implementation

Pull Request - State: closed - Opened by sunng87 10 months ago

#134 - Websocket example is not working

Issue - State: closed - Opened by mcorbin 10 months ago - 7 comments

#132 - Web transport server-side API

Issue - State: open - Opened by sunng87 11 months ago

#131 - feat: update ring to 1.12

Pull Request - State: closed - Opened by sunng87 11 months ago

#130 - fix: add back wrap jetty handler

Pull Request - State: closed - Opened by sunng87 11 months ago

#129 - feat: upgarde http3 module to latest QuicServerConnector api

Pull Request - State: closed - Opened by sunng87 12 months ago

#128 - `:wrap-jetty-handler` option no longer has any effect since 0.30/Jetty 12

Issue - State: closed - Opened by svdm 12 months ago - 2 comments

#127 - fix: allows async StreamableResponseBody

Pull Request - State: closed - Opened by sunng87 about 1 year ago

#126 - feat: add more options for websocket

Pull Request - State: closed - Opened by sunng87 about 1 year ago

#125 - Add `ws-configurator` parameter

Pull Request - State: closed - Opened by eneroth about 1 year ago - 1 comment

#124 - Websocket config

Issue - State: closed - Opened by eneroth about 1 year ago - 1 comment

#123 - debug logging of internal exception in case response can not be sent to client

Pull Request - State: closed - Opened by PawelWlodarski about 1 year ago - 2 comments

#122 - `write-body-to-stream` does not behave like in ring.adapter.jetty

Issue - State: open - Opened by chpill about 1 year ago - 6 comments

#121 - fix: ring websocket implementation fix

Pull Request - State: closed - Opened by sunng87 about 1 year ago

#120 - feat: jetty 12.0.4

Pull Request - State: closed - Opened by sunng87 about 1 year ago

#119 - Jetty 11.0.18

Issue - State: closed - Opened by seancorfield over 1 year ago - 2 comments

#118 - feat: upgrade jetty to 12.0.2 and improve buffered output stream

Pull Request - State: closed - Opened by sunng87 over 1 year ago - 2 comments

#118 - feat: upgrade jetty to 12.0.2 and improve buffered output stream

Pull Request - State: closed - Opened by sunng87 over 1 year ago - 2 comments

#117 - chore: pin Jetty version to 12.0.2

Pull Request - State: closed - Opened by matasaru over 1 year ago - 3 comments

#116 - feat: proof of concept implementation for ring.websocket

Pull Request - State: closed - Opened by sunng87 over 1 year ago

#115 - Ring websocket API compatibility

Issue - State: closed - Opened by weavejester over 1 year ago - 14 comments

#114 - fix: character encoding was previously returning content-type

Pull Request - State: closed - Opened by jasonjckn over 1 year ago - 2 comments

#113 - possible regression in 0.30.x, produces http status code 500, "Server Error"

Issue - State: closed - Opened by jasonjckn over 1 year ago - 16 comments

#112 - feat: add option to enable virtual threads support for thread pool

Pull Request - State: closed - Opened by sunng87 over 1 year ago - 8 comments

#111 - refactor(common): potentially avoid reflection

Pull Request - State: closed - Opened by jasonjckn over 1 year ago - 1 comment

#111 - refactor(common): potentially avoid reflection

Pull Request - State: closed - Opened by jasonjckn over 1 year ago - 1 comment

#110 - feat: port aysnc ring handler

Pull Request - State: closed - Opened by sunng87 over 1 year ago

#109 - feat: jetty12 websocket

Pull Request - State: closed - Opened by sunng87 over 1 year ago

#108 - Revert "feat: Implement jetty-core based websocket api for jetty 12"

Pull Request - State: closed - Opened by sunng87 over 1 year ago

#107 - feat: Implement jetty-core based websocket api for jetty 12

Pull Request - State: closed - Opened by sunng87 over 1 year ago

#106 - feat: Jetty 12

Pull Request - State: closed - Opened by sunng87 over 1 year ago - 26 comments

#105 - Jetty 12 adoption

Issue - State: closed - Opened by sunng87 over 1 year ago - 7 comments

#104 - c10k problem in jdk 21 with virtual threads.

Issue - State: open - Opened by jasonjckn over 1 year ago - 6 comments

#103 - feat: accept var as handler

Pull Request - State: closed - Opened by sunng87 over 1 year ago - 5 comments

#102 - run-jetty doesn't accept vars as handlers

Issue - State: closed - Opened by hiredman over 1 year ago - 2 comments
Labels: enhancement

#101 - Add configuration for quic and http3

Pull Request - State: closed - Opened by KsVlad almost 2 years ago

#100 - Http2 options

Pull Request - State: closed - Opened by KsVlad almost 2 years ago - 1 comment

#99 - HTTP2/3 connector/factory specific options in server config

Issue - State: closed - Opened by KsVlad almost 2 years ago - 8 comments

#98 - Update doc-string for ws-upgrade-response in websocket.clj

Pull Request - State: closed - Opened by hectorhon almost 2 years ago - 1 comment

#97 - Jetty's quice jna requires specific version of libquiche

Issue - State: closed - Opened by KsVlad almost 2 years ago - 2 comments

#96 - refactor!: rework/simplify implementation of SSL keystore hot-reload

Pull Request - State: closed - Opened by jimpil almost 2 years ago - 6 comments

#95 - v0.19.0 Responses without `:status` throw nullpointer exception

Issue - State: closed - Opened by M-sleeper almost 2 years ago - 3 comments

#94 - Rework the ssl-hot-reload-loop lifecycle, and revert return-type change in `run-jetty`

Pull Request - State: closed - Opened by jimpil almost 2 years ago - 3 comments

#93 - use `gen-class` for proxying handlers

Pull Request - State: closed - Opened by jimpil almost 2 years ago - 6 comments

#92 - Consider proxy-ing handlers in Java

Issue - State: closed - Opened by jimpil almost 2 years ago - 5 comments

#91 - Adds support for SSL certificate hot-reloading

Pull Request - State: closed - Opened by jimpil almost 2 years ago - 4 comments

#90 - Support hot-reload of certificate

Issue - State: closed - Opened by jimpil almost 2 years ago - 8 comments

#89 - [Question] Requesting assistance adding support for ring-jetty9-adapter to Sente

Issue - State: closed - Opened by ptaoussanis almost 2 years ago - 7 comments

#88 - Jetty 11.0.14 is available

Issue - State: closed - Opened by seancorfield almost 2 years ago - 2 comments

#87 - fix: add default value for ssl-port if ssl? enabled

Pull Request - State: closed - Opened by sunng87 about 2 years ago

#86 - Compilation issues do to missing dependencies

Pull Request - State: closed - Opened by Luke1298 about 2 years ago - 2 comments

#85 - :ssl-port param documentation needs improving

Issue - State: closed - Opened by jimpil about 2 years ago - 1 comment

#84 - Support the :async-timeout option

Pull Request - State: closed - Opened by fearnoeval about 2 years ago - 2 comments

#83 - fix: correct/add type hints to avoid reflection

Pull Request - State: closed - Opened by dekelpilli about 2 years ago - 4 comments

#82 - Project Loom is here and Jetty 10+ already supports it

Issue - State: closed - Opened by jimpil over 2 years ago - 28 comments

#81 - [DOCS] - Improve :thread-pool

Issue - State: closed - Opened by jimpil over 2 years ago - 1 comment

#80 - fix: allow both string and ExtensionConfig for :extensions

Pull Request - State: closed - Opened by sunng87 over 2 years ago

#79 - ws-handler as function does not work

Issue - State: closed - Opened by seancorfield over 2 years ago - 7 comments

#78 - Jetty 11?

Issue - State: closed - Opened by seancorfield over 2 years ago - 3 comments

#77 - Jetty 11 Support

Pull Request - State: closed - Opened by sundbry over 2 years ago - 1 comment

#76 - chore: setIdleTimeout requires a duration, not a long

Pull Request - State: closed - Opened by kkrausse over 2 years ago - 3 comments

#75 - Pass websocket options through to websocket handlers

Pull Request - State: closed - Opened by jamii over 2 years ago - 1 comment

#74 - :ws-max-text-message-size is ignored

Issue - State: closed - Opened by jamii over 2 years ago

#73 - Add support for SSLcontext

Pull Request - State: closed - Opened by mcorbin almost 3 years ago - 3 comments

#71 - fix: multi-arity implementation of close!

Pull Request - State: closed - Opened by sunng87 about 3 years ago

#70 - Wrong number of args error when calling single-argument version of close!

Issue - State: closed - Opened by paulbutcher about 3 years ago - 3 comments
Labels: bug

#69 - feat: implement http3 connector

Pull Request - State: closed - Opened by sunng87 about 3 years ago

#68 - http/3 support

Issue - State: closed - Opened by sunng87 about 3 years ago
Labels: enhancement

#67 - feat: add support for sni-required and sni-host-check

Pull Request - State: closed - Opened by sunng87 about 3 years ago

#66 - New options to support: sni-required? and sni-host-check?

Issue - State: closed - Opened by sunng87 about 3 years ago
Labels: enhancement

#65 - Fix warnings with handler usage and remove legacy websocket api

Pull Request - State: closed - Opened by sunng87 about 3 years ago

#64 - Jetty warnings

Issue - State: closed - Opened by sunng87 about 3 years ago

#63 - Server-sent events support

Issue - State: open - Opened by sunng87 about 3 years ago - 7 comments
Labels: enhancement

#62 - Fix websocket upgrade on Firefox.

Pull Request - State: closed - Opened by niwinz about 3 years ago - 1 comment

#61 - `ws-upgrade-request?` doesn't always works.

Issue - State: closed - Opened by niwinz about 3 years ago - 2 comments

#60 - Websocket API, examples and docs revamp

Pull Request - State: closed - Opened by sunng87 over 3 years ago

#59 - Add support for websocket protocol upgrade.

Pull Request - State: closed - Opened by celiocidral over 3 years ago - 6 comments

#58 - Support for closing websocket with status code and reason.

Pull Request - State: closed - Opened by celiocidral over 3 years ago - 1 comment

#57 - Supporting :keystore-scan-interval like the main Jetty adapter

Issue - State: closed - Opened by TuggyNE over 3 years ago - 3 comments

#56 - Jetty 10

Pull Request - State: closed - Opened by sunng87 about 4 years ago

#55 - Adds support for ping/pong listener, and a `ping!` fn

Pull Request - State: closed - Opened by crinklywrappr about 4 years ago - 1 comment

#54 - Jetty 10 support

Issue - State: closed - Opened by sunng87 about 4 years ago - 2 comments

#53 - Lazy behaviour for websocket `msg`?

Issue - State: closed - Opened by refset over 4 years ago - 1 comment

#52 - SslContextFactory, reflection warnings, tests

Pull Request - State: closed - Opened by wavejumper over 4 years ago - 2 comments

#51 - Allow for custom ws-adpater

Pull Request - State: closed - Opened by wavejumper over 4 years ago - 2 comments

#50 - Conscrypt lib not working on JDK11

Issue - State: closed - Opened by raymcdermott over 4 years ago - 3 comments

#49 - `run-jetty` never returning from join

Issue - State: closed - Opened by dpetranek over 4 years ago - 3 comments

#48 - (feat) subprotocol and extension negotiation support [#47]

Pull Request - State: closed - Opened by sunng87 almost 5 years ago

#47 - Proper websocket handshake when subprotocols provided

Issue - State: closed - Opened by sunng87 almost 5 years ago