Hi Sascha,

Fix is at https://github.com/jenkinsci/build-flow-plugin/pull/42 if you 
want to get the source and do a local build.
Otherwise wait for the code to be accepted and either grab the latest build 
from Jenkins, or wait for the release.

/James

On Friday, 4 April 2014 08:36:24 UTC+1, Sascha Herrmann wrote:
>
> Thanks for your reply.
>
> Yes, using Fiddler, the last request I see before the error is a GET to
>
>
> http://<server>/job/<job_name>/descriptorByName/com.cloudbees.plugins.flow.BuildFlow/checkDsl?value=.......
>
> with value being the encoded text of the DSL. The DSL itself is some 3900 
> characters. Then add the encoding overhead. The GET request is then some 
> 6522 bytes.
>
> When you talk about a fix ... how would we get the fix? Will it go into 
> the next plugin version?
>
> Sascha
>
> Am Mittwoch, 2. April 2014 22:36:57 UTC+2 schrieb teilo:
>>
>> Sounds like the flow is validating the dsl via a http get request.
>> If the flow is large the http request will be too large for some severs 
>> to handle. This intern causes some headers to be lost on  the server, to 
>> which jenkins will the think you are not authenticated and will clear your 
>> cookie...
>>
>> I don't see anything in the code to force it to use http post, but I'm 
>> away from my pc for a while so can't check and fix, should be a few lines 
>> to change if I am correct at the cause.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to