From: Christopher F. <chr...@ca...> - 2014-11-04 08:53:13
|
On 03/11/2014 23:08, Devangana Tarafdar wrote: > Hello, > > I have a simple yaws web page that accepts a post data through a > textarea field. There is only one data input field on this page. On the > next page it displays the data that was fed in along with a "confirm" > submit button. There is also a hidden field containing the data that was > fed in. > > When I use the w3m client, posting large data occasionally causes the > text on the following page to be truncated. > > As "large data" I am submitting a list that looks somewhat like > this:(There is only one element shown, I have seen this issue by > submitting a list with 3 such elements or more, but again , sometimes > everything works with 3 elements and then the problem comes up if I add > more list elements): > > [ > {my_test_proplist, > [{enabled,true}, > {id,test_beta2}, > {sql, > "select * from test_view with (nolock) order by app_id asc, > behavior_type asc, priority asc, behavior_id asc"}, > {mnesia_tabdef, > [{type,bag}, > {attributes, > [{app_id,integer}, > {rule_id,integer}, > {behavior_id,integer}, > {behavior_name,string}, > {behavior_type,integer}, > {policy_name,string}, > {priority,integer}, > {criterion,string}, > {platform_value,integer}]}]}, > {sync_interval_ms,-1}, > {sync_mode,full}] > }, > > {....}, > {....} > ] > > I am using 2 builds of yaws 1.96 , one built from source on linux centos > 6.3 and the other is yaws 1.96 built from source on solaris 10 and I see > this issue only with the linux build. I have not been able to reproduce > this with the solaris 10 build at all. > W3M version is w3m/0.5.2. <http://0.5.2.> , running on a ubuntu box and > sometimes I use it from a centOS box. > > I don't know if this is a yaws or a w3m issue, any guidance will be > appreciated. > Hi, I don't have enough data to understand exactly where your problem come from. Your use case is pretty simple and should work fine. Can you provide us with the yaws scripts you use to be sure ? You could also enable traces in Yaws to dump content of the requests and the responses. It is a simple way to see inputs/outputs from Yaws point of view. The trace files will be written in your logdir, in a subdirectory trace_<YYYYMMDD_hhmmss>. To enable trace, you should set the parameter "trace" to http or traffic in your yaws.conf file. See http://yaws.hyber.org/yman.yaws?page=yaws.conf for details. -- Christopher |