Handling of 204 HTTP status codes
Locked
Handling of 204 HTTP status codes
 
|
Hi all My version of the RestEasy framework returns a 204 status code, if my Restful WS call's response is empty. The reaction of the xforms engine is, that the browser's page is not updated (that's OK), but the "Loading …" sign does not disappear. If the server sends a 200 response code, the empty response page is shown, and the "Loading …" sign disappears correctly. Any hints how to fix this? Best regards, Simon
-- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Re: Handling of 204 HTTP status codes
|
|
Hi Simon, A workaround is not to show the loading message at all, on the submission element: xxforms:show-progress="false" --Hank On Aug 13, 2010, at 1:03 AM, Gunzenreiner Simon wrote:
Hank Ratzesberger NEES@UCSB Earth Research Institute University of California, Santa Barbara 805-893-8042 -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
AW: Re: Handling of 204 HTTP status codes
|
|
Hi Hank Good hint. In the meantime I made sure that I only get 200
instead of 204 status codes. But – would you agree that it is a bug, in other
words, should I report it in the bug tracker. I am always hesitant in reporting
some behavior as a bug, and in the end it turns out it is a correct behavior … Regards Simon Von: Hank
Ratzesberger [mailto:[hidden email]] Hi Simon, A workaround is not to show the
loading message at all, on the submission element: xxforms:show-progress="false" --Hank On Aug 13, 2010, at 1:03 AM,
Gunzenreiner Simon wrote:
Hi all My version of the RestEasy framework returns
a 204 status code, if my Restful WS call's response
is empty. The reaction of the xforms engine is, that
the browser's page is not updated (that's OK), but the "Loading …" sign
does not disappear. If the server sends a 200 response code, the empty response
page is shown, and the "Loading …"
sign disappears correctly. Any hints how to fix this? Best regards, Simon
Hank
Ratzesberger NEES@UCSB Earth
Research Institute University
of California, Santa Barbara 805-893-8042 -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Re: AW: Re: Handling of 204 HTTP status codes
|
|
Hi Simon, I would report it at this point, and if there are other reasons, then they can respond -- and if anyone is looking there later, they might find the notes. Best, Hank Quoting Gunzenreiner Simon <[hidden email]>: > Hi Hank > > > > Good hint. In the meantime I made sure that I only get 200 instead of > 204 status codes. But - would you agree that it is a bug, in other > words, should I report it in the bug tracker. I am always hesitant in > reporting some behavior as a bug, and in the end it turns out it is a > correct behavior ... > > > > Regards > > Simon > > > > Von: Hank Ratzesberger [mailto:[hidden email]] > Gesendet: Freitag, 13. August 2010 23:23 > An: [hidden email] > Betreff: [ops-users] Re: Handling of 204 HTTP status codes > > > > > > Hi Simon, > > > > A workaround is not to show the loading message at all, on the > submission element: > > > > xxforms:show-progress="false" > > > > --Hank > > > > On Aug 13, 2010, at 1:03 AM, Gunzenreiner Simon wrote: > > > > > > Hi all > > My version of the RestEasy framework returns a 204 status code, if my > Restful WS call's response is empty. The reaction of the xforms engine > is, that the browser's page is not updated (that's OK), but the "Loading > ..." sign does not disappear. If the server sends a 200 response code, > the empty response page is shown, and the "Loading ..." sign disappears > correctly. > > Any hints how to fix this? > > Best regards, > > Simon > > > > > -- > You receive this message as a subscriber of the [hidden email] > mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > > > Hank Ratzesberger > > NEES@UCSB > > Earth Research Institute > > University of California, Santa Barbara > > 805-893-8042 > > > > > > > > > > > > -- Hank Ratzesberger [hidden email] -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Re: Re: AW: Re: Handling of 204 HTTP status codes
|
Administrator
|
Simon,
That might well be a bug if it works with 200 but not 204. In XFormsModelSubmission.java [1], though, we test like this: if (connectionResult.statusCode >= 200 && connectionResult.statusCode < 300) So the issue must be somewhere else. Do you have a simple reproducible case? -Erik [1] http://github.com/orbeon/orbeon-forms/blob/master/src/java/org/orbeon/oxf/xforms/submission/XFormsModelSubmission.java On Sat, Aug 14, 2010 at 10:39 AM, Louis Ratzesberger <[hidden email]> wrote: > > Hi Simon, > > I would report it at this point, and if there are other reasons, then they > can respond -- and if anyone is looking there later, they might find > the notes. > > Best, > Hank > > Quoting Gunzenreiner Simon <[hidden email]>: > >> Hi Hank >> >> >> >> Good hint. In the meantime I made sure that I only get 200 instead of >> 204 status codes. But - would you agree that it is a bug, in other >> words, should I report it in the bug tracker. I am always hesitant in >> reporting some behavior as a bug, and in the end it turns out it is a >> correct behavior ... >> >> >> >> Regards >> >> Simon >> >> >> >> Von: Hank Ratzesberger [mailto:[hidden email]] >> Gesendet: Freitag, 13. August 2010 23:23 >> An: [hidden email] >> Betreff: [ops-users] Re: Handling of 204 HTTP status codes >> >> >> >> >> >> Hi Simon, >> >> >> >> A workaround is not to show the loading message at all, on the >> submission element: >> >> >> >> xxforms:show-progress="false" >> >> >> >> --Hank >> >> >> >> On Aug 13, 2010, at 1:03 AM, Gunzenreiner Simon wrote: >> >> >> >> >> >> Hi all >> >> My version of the RestEasy framework returns a 204 status code, if my >> Restful WS call's response is empty. The reaction of the xforms engine >> is, that the browser's page is not updated (that's OK), but the "Loading >> ..." sign does not disappear. If the server sends a 200 response code, >> the empty response page is shown, and the "Loading ..." sign disappears >> correctly. >> >> Any hints how to fix this? >> >> Best regards, >> >> Simon >> >> >> >> >> -- >> You receive this message as a subscriber of the [hidden email] >> mailing list. >> To unsubscribe: mailto:[hidden email] >> For general help: mailto:[hidden email]?subject=help >> OW2 mailing lists service home page: http://www.ow2.org/wws >> >> >> >> Hank Ratzesberger >> >> NEES@UCSB >> >> Earth Research Institute >> >> University of California, Santa Barbara >> >> 805-893-8042 >> >> >> >> >> >> >> >> >> >> >> >> > > > > -- > Hank Ratzesberger > [hidden email] > > > > -- > You receive this message as a subscriber of the [hidden email] mailing > list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
| Free forum by Nabble | Edit this page |