wf:update problem on large Post on Yaws

#93

The wf:update don't send the POST in chunks and when the post data is more than 10240 (The default of yaws) then
error from yaws api fires:
{error,error,function_clause,

   [{yaws_api,do_parse_spec,
              [{partial,<<"pageContext= ...... ">>}, 
               ['ALLSTRINGS'],
               nokey,[],key]},
    {wf_core,deserialize_context,0},
    {wf_core,run_catched,0},
    {wf_core,run,0},
    {yaws_server,deliver_dyn_part,8},
    {yaws_server,aloop,3},
    {yaws_server,acceptor0,2},
    {proc_lib,init_p_do_apply,3}]}

The workaround is to set the following on yaws config.
partial_post_size = nolimit

Reported by Panagiotis Skarvelis · August 21st, 2010 @ 04:47 AM

Activity

Val
wf:update seems pile up elements. Is it intended or just side effect?
For sample I set #panel with #textbox in it. After some updating the #panel on
wf:q(.. ) got error and on wf:qs(...) got all the inputs in #textbox from past XX updates.
It is killing my yaws too.
So partial_post_size = nolimit solved some problem, but how to
get rid of unwanted clotting?

September 10th, 2010 @ 05:08 PM
ELROR
Hi,

I've hit the same problem creating a browser for riak.

I'm sending quite a lot of buttons (as I have lots of buckets/keys), and after clicking them I end up with an error like this.

It's not a huge problem for me at the moment but I'd like to know if there is a fix/workaround.

June 30th, 2011 @ 04:28 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.