Topic
1 reply Latest Post - ‏2012-12-13T09:43:29Z by HermannSW
SystemAdmin
SystemAdmin
6772 Posts
ACCEPTED ANSWER

Pinned topic Message Size enforcement

‏2012-12-12T17:43:10Z |
Is it possible to reject a connection, once a certain number of bytes are received on the front side handler.

Thinking in terms of large file/message being posted to Datapower, unless message is received and processed by xml manager there is no way to determine the size.
But by the time message is received and processed by xml manager the message is already on the datapower.
So is it possible to cut off transaction after certain bytes are received without accepting anymore.

thanks
Updated on 2012-12-13T09:43:29Z at 2012-12-13T09:43:29Z by HermannSW
  • HermannSW
    HermannSW
    4124 Posts
    ACCEPTED ANSWER

    Re: Message Size enforcement

    ‏2012-12-13T09:43:29Z  in response to SystemAdmin
    > Is it possible to reject a connection, once a certain number of bytes are received on the front side handler.
    >
    yes.

    > Thinking in terms of large file/message being posted to Datapower, unless message is received and processed by xml manager there is no way to determine the size.
    > But by the time message is received and processed by xml manager the message is already on the datapower.
    > So is it possible to cut off transaction after certain bytes are received without accepting anymore.
    >
    That is exactly what DataPower's "XML Threat Protection" allows you to specify.
    What you ask for is "XML Bytes Scanned" (by default restricted to 4194304 bytes), as you can see below you can restrict several other values.
    You find that "XML Parser" tab in your XML Manager, see below.
    In case of Non-XML request type you can restrict the "Max. Message Size", but under the "Threat Protection" tab of your service.


     
    Hermann<myXsltBlog/> <myXsltTweets/>