java.net.ProtocolException: Expected HTTP 101 response but was '400 Bad Request'

Google Groups | Henry Saputra | 7 months ago
  1. 0

    What is the latest version of kubernetes-client that support K8S 1.1 version

    Google Groups | 7 months ago | Henry Saputra
    java.net.ProtocolException: Expected HTTP 101 response but was '400 Bad Request'
  2. 0

    Kubernetes client eat up exception from call to adding watch

    GitHub | 7 months ago | hsaputra
    java.net.ProtocolException: Expected HTTP 101 response but was '400 Bad Request'
  3. 0

    GitHub comment 496#257726048

    GitHub | 1 month ago | akroston
    java.net.ProtocolException: Expected HTTP 101 response but was '200 OK'
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 2289#245163981

    GitHub | 3 months ago | rarora13
    java.net.ProtocolException: Expected HTTP 101 response but was '503 Endpoint Creation Failed'
  6. 0

    Expected HTTP 101 response but was '500 Internal Server Error'

    GitHub | 10 months ago | rawlingsj
    java.net.ProtocolException: Expected HTTP 101 response but was '500 Internal Server Error'

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.net.ProtocolException

      Expected HTTP 101 response but was '400 Bad Request'

      at com.squareup.okhttp.ws.WebSocketCall.createWebSocket()
    2. com.squareup.okhttp
      WebSocketCall.access$000
      1. com.squareup.okhttp.ws.WebSocketCall.createWebSocket(WebSocketCall.java:123)
      2. com.squareup.okhttp.ws.WebSocketCall.access$000(WebSocketCall.java:40)
      2 frames