pusher/pusher-http-dotnet

Issues

• An attempt was made to access a socket in a way forbidden by its access permissions

  #94 opened 10 months ago by NareshBanala-dev
  1

• Exception thrown windows machine with FIPS enabled

  #95 opened a year ago by marknadig
  1

• Reporting a vulnerability

  #91 opened 2 years ago by igibek
  1

• InvalidOperationException "You cannot trigger to multiple channels when using encrypted channels."

  #87 opened 2 years ago by m3taphysics
  2

• System.IO.IOException: The response ended prematurely.

  #86 opened 2 years ago by pbiggar
  7

• Need clearer documentation on the recommended lifetime of Pusher, PusherOptions

  #83 opened 3 years ago by burns47
  1

• App key romaniaroleplay2021 not in this cluster. Did you forget to specify the cluster?

  #84 opened 3 years ago by flaspu
  1

• What should be the scope of Pusher instance

  #82 opened 3 years ago by TailyFair
  2

• Improved error handling of trigger requests

  #58 opened 4 years ago by benw-pusher
  1

• Add option for configurable argument for timeout

  #61 opened 4 years ago by ccaseypusher
  2

• eventName might contain double escaped strings

  #60 opened 4 years ago by lukepower
  3

• Authentication failed because the remote party has closed the transport stream.

  #49 opened 4 years ago by AngeloAnolin
  1

• Provide an option to triggerAsync on already serialsied data

  #63 opened 4 years ago by jackkettle
  1

• Application never gets connected to Pusher

  #62 opened 4 years ago
  2

• Better logging solution

  #6 opened 4 years ago by leggetter
  0

• Support .NET Standard

  #47 opened 4 years ago by andrewlock
  14

• Using PursherClient library in .Net Framework 4.7 gets an error in TriggerAsync

  #67 opened 4 years ago by sergiohj
  2

• TriggerResult exception text should include content

  #56 opened 4 years ago by marknadig
  0

• Pusher : Error : {"type":"WebSocketError","error":{"type":"PusherError","data":{"code":4001,"message":"App key 914447 not in this cluster. Did you forget to specify the cluster?"}}}

  #59 opened 5 years ago by jph6366
  1

• The response body from the Pusher HTTP endpoint could not be parsed as JSON

  #42 opened 7 years ago by lukpep
  3

• App key "Key"not in this cluster. Did you forget to specify the cluster?

  #50 opened 6 years ago by Ruben1701
  1

• Error with dotnet client

  #44 opened 7 years ago by galgitron
  25

• Pusher: TriggerResponseException

  #45 opened 7 years ago by fred5577
  4

• Random exception

  #29 opened 7 years ago by davidebettio
  6

• No notify when device was offline

  #43 opened 7 years ago by ImanX
  1

• Data payload in Trigger returning Microsoft DateFormat

  #35 opened 7 years ago by fahyik
  2

• Could not load file or assembly 'RestSharp, Version=105.0.1.0

  #36 opened 8 years ago by iw-cnickeson
  2

• TriggerAsync returning void?

  #37 opened 8 years ago by jcd79
  3

• ASP.net Core Support

  #27 opened 8 years ago by yehiasalam
  2

• Add support for mono & builds on unix

  #1 opened 8 years ago by cultureulterior
  1

• Update nuget feed with the latest version.

  #24 opened 9 years ago by abeninskibede
  4

• introduce the cluster option

  #22 opened 9 years ago by topliceanu
  0

• Run unit tests as part of Travis build

  #8 opened 9 years ago by leggetter
  1

• Broken due to breaking change in RestSharp

  #3 opened 10 years ago by drewf
  3