java.lang.AssertionError: Response Status Code Expected: is <400> but: was <405>

GitHub | joakime | 4 months ago
  1. 0

    Invalid WebSocket Upgrade should result in error 400, not 405

    GitHub | 4 months ago | joakime
    java.lang.AssertionError: Response Status Code Expected: is <400> but: was <405>
  2. 0

    Java.lang.AssertionError: Status expected:<200> but was:<405> - scriptscoop.com

    scriptscoop.com | 1 year ago
    java.lang.AssertionError: Status expected:<200> but was:<405>
  3. 0

    How to make unit test multipart with a PUT request using Spring MVC and Spock?

    Stack Overflow | 7 months ago | Juan Caleb Rizo Vilchis
    java.lang.AssertionError: Status expected:<201> but was:<405>
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    java.lang.AssertionError: Status expected:<200> but was:<405>

    Stack Overflow | 3 years ago | gstackoverflow
    java.lang.AssertionError: Status expected:<200> but was:<405>
  6. 0

    Spring test + servlet 3.0 + multipart-config tag

    Stack Overflow | 3 years ago | Beto Neto
    java.lang.AssertionError: Status expected:<200> but was:<400>

    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.lang.AssertionError

      Response Status Code Expected: is <400> but: was <405>

      at org.eclipse.jetty.websocket.server.WebSocketInvalidVersionTest.testRequestVersion29()
    2. Jetty
      WebSocketInvalidVersionTest.testRequestVersion29
      1. org.eclipse.jetty.websocket.server.WebSocketInvalidVersionTest.testRequestVersion29(WebSocketInvalidVersionTest.java:64)
      1 frame