This is a fix for issue #188. The response filter creates a
PostbackParser instance for all postbacks, but it should only create the
PostbackParser instance for async Ajax postbacks, otherwise regular page
postbacks are parsed unnecessarily and can even cause the entire page to
cause an exception (this happens if the page has a pipe symbol anywhere
in the content). This change adds a test so that the PostbackParser
instance is only created for async Ajax postbacks.
Two further considerations:
Making this even more robust and check that actual formatting of the
postback.
Rename PostbackParser because the parser does not parse all
postbacks, rather only async Ajax postbacks.
This is a fix for issue #188. The response filter creates a PostbackParser instance for all postbacks, but it should only create the PostbackParser instance for async Ajax postbacks, otherwise regular page postbacks are parsed unnecessarily and can even cause the entire page to cause an exception (this happens if the page has a pipe symbol anywhere in the content). This change adds a test so that the PostbackParser instance is only created for async Ajax postbacks.
Two further considerations: