Partial Broken Site Access

  • Resolved poppuser

    (@poppuser)


    2 years, 3 months ago

    Since I updated the Breeze plugin our site this morning, an automated program I have that simply uses an HttpClient (C#) to access the pages of the site can no longer reach them. It receives a 500 error when simply performing an HTTP GET on the pages.

    If I access those same pages from a browser, no error.

    If I disable the Breeze Plugin… no error.

    It was working fine up until this mornings updates, not sure if it was 2.1.1 or 2.1.2 that causes the problem.

    Not even sure where to begin debugging this when my program and the web browser are using the same protocols to access the site, so makes no sense that one works and the other doesn’t.

    Any ideas ?

    • This topic was modified 2 years, 3 months ago by poppuser.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter poppuser

    (@poppuser)

    2 years, 3 months ago

    To expound on it… I am receiving a 500 Server Error when it fails from the program access. No such error when using web browser.

    Have also tried switching the HTTP version being used to access the site from HTTP/1.1 to HTTP/2 and same error persists.

    Plugin Author adeelkhan

    (@adeelkhan)

    2 years, 3 months ago

    Kindly review the error log to pinpoint the source of the conflict.

    Thread Starter poppuser

    (@poppuser)

    2 years, 3 months ago

    So… here is what I found.

    Apparently the Breeze Plugin now requires that the Header in the HTTP communication contain a “User-Agent” header. Up to the latest releases, that was NOT required. So when my application was accessing it Breeze was throwing out a 500 Error. As soon as I added in that header, all was well.

    I did however also run into some issues with the GZip compression being active. Either that wasn’t working before or something changed so that my application cannot “read” the streamed data. Not sure what changed, but I had to turn off Gzip compression in order to get my application to work with it. Again, this worked just fine (with GZip turned on) up until the most recent Breeze release.

    Hopefully that info helps someone else in debugging strange errors appearing that were never there before 🙂

    Plugin Author adeelkhan

    (@adeelkhan)

    2 years, 3 months ago

    Thank you for providing the details, and I’m pleased to hear that you’ve identified a workaround for the broken site access.

    Regarding Gzip, are there any warnings or errors appearing in the console log or debug log?

    Plugin Author adeelkhan

    (@adeelkhan)

    2 years, 3 months ago

    Please share the logs.

    Plugin Author adeelkhan

    (@adeelkhan)

    2 years, 3 months ago

    I would like to bring to your attention the release of the latest build, Breeze version 2.1.3.
    This update includes a significant improvement in the system’s functionality, specifically addressing cases where no “HTTP_USER_AGENT” header is sent. The enhancement ensures a more robust and seamless experience for users in various scenarios.
    To benefit from these improvements, kindly update to Breeze version 2.1.3 at your earliest convenience.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Partial Broken Site Access’ is closed to new replies.