Re: Hidden fields in forms

[Gary F. <ga...@iF...>]

If you email the source files, I'll take a look. No guarantees. Even if I can make the changes, I won't be able to test the result -- that would be up to you.

Gary


On Jun 25, 2010, at 2:24 AM, Peter Becker wrote:

Many thanks Gary for your most helpful reply.

I had read the section in the documentation on RESPONSE_TOKEN many times, and unfortunately it does not have the detail you provided here.   As you point out, I need a feature which curl-loader cannot at present do.
 
This is probably a common issue, as the security feature I encountered is part of a standard Django/Python framework.  It is most disapointing that you don't have access to a system!  Its probably a small change - just to look for a slightly different pattern: /name="x" value="y"/ instead of /x="y"/.  Is there any way we can arrange to add this to the code?  As per my first post, I found the section of code which applies, but getting to understand it all was a bit daunting: scan_response/keyval_scan/kv_scan/scan_for_key/bitap_search...  If I email you the source, please could you outline the change(s) needed, and I can implement them?  I am fluent in C, so you would just have to give a little assistance...  
 
(This is, of course, only applicable if the current developer team are not willing to assist with this!)
 
Kind regards,
Peter