I had the something similar more that one year ago:
we did something like this in the delegate which had the service instance

            service.method = "POST";
            service.contentType = "application/x-www-form-urlencoded";
            var call : Object = service.send({test:"ping"});

In our case the issue with the netscaler was messing with the requests and was 
not able to consume empty GET/POST requests, so it kept rejecting them as 
invalid when the first empty GET/POST.

HTH,
C


________________________________
From: murugs73 <[email protected]>
To: [email protected]
Sent: Fri, March 5, 2010 5:54:32 PM
Subject: [flexcoders] Re: Issue in Flex application deployed in Load balanced 
environment

   
Hi, 
I do have the same issue, when flex app is deployed behind the load balancer, 
where ssl is terminated. Please let me know, how i can resolve this..

Thanks
Murugan.

--- In flexcod...@yahoogro ups.com, abhgup <abhishek.gupta@ ...> wrote:
>
> 
> I have developed the dashboard in my application using flex 3.0. For this I
> have used JSP wrapper around the flex application. My application runs on
> JBoss application server. for communication between flex app and my
> application i am using LCDS. HTTPService component is being used to receive
> data from the server. Channel definitions are given in service-config. xml
> for amf and http channels and for both secure secure and not secure mode. In
> my proxy-config. xml i have defined Channels and destinations.
> 
> 
> 
> services-config. xml
> 
> ...
> ...
> 
> <channel-definition id="my-amf" class="mx.messaging .channels. AMFChannel" >
>     <endpoint
> url="http:// {server.name} :{server. port}/{context. root}/messagebro ker/amf"
> class="flex. messaging. endpoints. AMFEndpoint" />
>     <properties>
>           <polling-enabled> false</polling- enabled>
>     </properties>
> </channel-definitio n>
> 
> <channel-definition id="my-secure- amf"
> class="mx.messaging .channels. SecureAMFChannel ">
>     <endpoint
> url="https:/ /{server. name}:{server. port}/{context. root}/messagebro 
> ker/amfsecure"
> class="flex. messaging. endpoints. SecureAMFEndpoin t"/>
>     <properties>
>           <add-no-cache- headers>false< /add-no-cache- headers>
>     </properties>
> </channel-definitio n>
> 
> <channel-definition id="my-http" class="mx.messaging .channels. HTTPChannel" >
>     <endpoint
> url="http:// {server.name} :{server. port}/{context. root}/messagebro 
> ker/http"
> class="flex. messaging. endpoints. HTTPEndpoint" />
> </channel-definitio n>
> 
> <channel-definition id="my-secure- http"
> class="mx.messaging .channels. SecureHTTPChanne l">
>     <endpoint
> url="https:/ /{server. name}:{server. port}/{context. root}/messagebro 
> ker/httpsecure"
> class="flex. messaging. endpoints. SecureHTTPEndpoi nt"/>
>     <properties>
>         <add-no-cache- headers>false< /add-no-cache- headers>
>     </properties>
> </channel-definitio n>
> 
> 
> ...
> ...
> 
> 
> 
> proxy-config. xml
> 
> 
> 
> ...
> ...
> 
> <default-channels>
>     <channel ref="my-http" />
>     <channel ref="my-amf" />
>     <channel ref="my-secure- http"/>
>     <channel ref="my-secure- amf"/>
> </default-channels>
> 
> ...
> ...
> 
> <destination id="dashboardServic e">
>     <properties>
> <url>/kr/servlet/ DashboardServlet </url>
>     </properties>
> </destination>
> 
> <destination id="dashboardJSPSer vice">
>     <properties>
> <url>/kr/krportal/ dashboardJSPServ ice.jsf</ url>
>     </properties>
> </destination>
> 
> 
> 
> ...
> 
> ...
> 
> 
> 
> In my development environment both secure and non secure mode were working
> fine. Now when I have deployed it behind the load balancer(which accepts
> secure requests only and if the request is not secure it redirects it to
> secure url) there is no response from the message broker servlet. One thing
> more I have observed is when the environment is non load balanced there are
> request like
> 'http://{server. name}:{server. port}/{context. root}/messagebro ker/http' . 
> and
> these requests are post request. But in load balanced environment with ssl
> the request is again like
> 'http://{server. name}:{server. port}/{context. root}/messagebro ker/http' 
> which
> is a post request and it is redirected to
> 'https://{server. name}:{server. port}/{context. root}/messagebro ker/http'
> which is a get request. The content returned by this get request is null.
> 
> 
> 
> Looking for some comments
> 
> 
> 
> Thanks
> 
> Abhishek Gupta 
> -- 
> View this message in context: http://old.nabble. com/Issue- in-Flex-applicat 
> ion-deployed- in-Load-balanced -environment- tp26156027p26156 027.html
> Sent from the FlexCoders mailing list archive at Nabble.com.
>


 


      

Reply via email to