Fiddler2 reports that the request is aborted most of the time. But some
request gets this warning from Fiddler2:



369         Content-Length mismatch: Request Header indicated 95 876 bytes,
but client sent 65 536 bytes.

369         Failed to obtain request body. System.IO.InvalidDataException
The request body did not contain the specified number of bytes. Got 65536,
expected 95876



This is the situation where _state = -13 and RequestParameter is null.
The request should be thrown and never call any methods which can lead
to unexpected result. Isn't this a security issue too?



Maybe this is a jetty bug?





<*groupId*>org.mortbay.jetty</*groupId*>
<*artifactId*>maven-jetty-plugin</*artifactId*>
<*version*>6.1.16</*version*>



*From:* Lance Java [via Apache Tapestry Mailing List Archives] [mailto:
ml-node+s1045711n5730616...@n5.nabble.com]
*Sent:* 8. mai 2015 17:43
*To:* Svein
*Subject:* RE: Detect jqXHR.abort()



Ah, sorry... It looks like the browser actually closes the connection on
abort which is resulting in a partial request being sent to the server. I
have no idea how to detect this (possibly different per container too).

Since you've found a solution which doesn't abort I'd use that.

Cheers,
Lance.

------------------------------

*If you reply to this email, your message will be added to the discussion
below:*

http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Detect-jqXHR-abort-tp5730595p5730616.html

To unsubscribe from users@tapestry.apache.org Mailing List Archives, click
here
<http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2375125&code=c3ZlaW5AamFjaWxsYS5ub3wyMzc1MTI1fC0xNTM4NzY2ODg4>
.
NAML
<http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

Reply via email to