Skip to Content

Linting failing in WebIDE (Full Stack) Websocket requests failing

Websocket (wss) requests for the linting of code in WebIde is failing on one particular client of mine. The network people are investigating and we think it is a similar scenario to

Requests of the form wss://[tenant-id] are returning 404.

We are guessing that the lack of sticky sessions on the proxy means that web socket requests are not sent with the same auth and thus failing.

Has anyone had this experience? or overcome it?



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Nov 22, 2018 at 11:20 AM

    Hi Nigel,

    When you say client you mean a particular browser or machine?

    Does the problem reproduce on all browsers?

    Could you share the request and response headers from your browser developer tools?



    Add comment
    10|10000 characters needed characters exceeded

  • Nov 22, 2018 at 11:44 PM

    Client - a phrase which here means* "person or organisation using the services of a lawyer or other professional person or company."

    So at this client their network set up is such that WSS requests fail and as such no linting for webide.

    For all browsers inside this network this is the state of play.

    When I use Webide outside this network environment everything works as expected in all browsers.

    Here is the header. Everything else is just keys and cookies ( and tim-tams)

    Request URL: wss://[tenantid][appname]/eslint 
    Request Method: GET Status Code: 404 Not Found

    Let me know if anything thing else would be useful.

    We think it is a sticky sessions issues (or lack thereof) but wondering if anyone else has come across this.



    * with apologies to Lemony Snicket

    Add comment
    10|10000 characters needed characters exceeded