By looking at your server and client configurations: Try consistent configuration across client and server. For example:
- Your server is map(listening) to port 81 but you try to connect through port 443. - Your server domain config should equal the domain config in the client. For server you have behindf5.com and for client have InFrontOfF5.com NOTE: You dont have to host the APE_JSF in the same domain as the ape server On Oct 26, 2011 12:34 PM, "chrismdodson" < [email protected]> wrote: > > Hi there: > > Setting up APE 1.1.1 behind an F5 load balancer, which is performing > SSL offloading (so behind F5 no SSL). The server config looks like > this: (running as root – what is impact of not using daemon user and > group?) > > uid { > # "aped" switch to this user/group if it run as root > user = daemon > group = daemon > } > > > Server { > port = 81 > daemon = no > ip_listen = xxx.xxx.xxx.xxx (do not want to > divulge!) > domain = behindF5.com (do not want to divulge!) > rlimit_nofile = 10000 > pid_file = ./aped.pid > } > > Log { > debug = 1 > use_syslog = 0 > syslog_facility = local2 > logfile = ./ape.log > } > > JSONP { > eval_func = Ape.transport.read > allowed = 1 > } > > Config { > #relative to ape.conf > modules = ../modules/lib/ > modules_conf = ../modules/conf/ > } > > The APE_JSF looks like this: > > APE.Config.baseUrl = 'https://InFrontOfF5.com/APE_JSF'; //APE JSF > (do not want to divulge!) > APE.Config.domain = 'InFrontOfF5.com'; > APE.Config.server = 'ApeInFrontOfF5.com:443'; //APE server URL > APE.Config.secure = true; > > (function(){ > for (var i = 0; i < arguments.length; i++) > APE.Config.scripts.push(APE.Config.baseUrl + '/ > Source/' + arguments[i] + '.js'); > })('mootools-core', 'Core/APE', 'Core/Events', 'Core/Core', 'Pipe/ > Pipe', 'Pipe/PipeProxy', 'Pipe/PipeMulti', 'Pipe/PipeSingle', 'Request/ > Request','Request/Request.Stack', 'Request/Request.CycledStack', > 'Transport/Transport.longPolling','Transport/Transport.SSE', > 'Transport/Transport.XHRStreaming', 'Transport/Transport.JSONP', > 'Transport/Transport.WebSocket', 'Core/Utility', 'Core/JSON'); > > > Then I changed the test script per Jason Morriss’s post in this group > on Aug31 2010, so that https is attempted rather than http to > 'ApeInFrontOfF5:443' (have also tried without Jason’s changes) > > However I just get: > > Running test : Init > Running test : Loading Client > Running test : Loading config > Config values are : > identifier : ape > init : true > frequency : 0 > scripts : > > https://InFrontOfF5.com/APE_JSF/Source/mootools-core.js,https://InFrontOfF5.com/APE_JSF/Source/Core/APE.js,https://InFrontOfF5.com/APE_JSF/Source/Core/Events.js,https://InFrontOfF5.com/APE_JSF/Source/Core/Core.js,https://InFrontOfF5.com/APE_JSF/Source/Pipe/Pipe.js,https://InFrontOfF5.com/APE_JSF/Source/Pipe/PipeProxy.js,https://InFrontOfF5.com/APE_JSF/Source/Pipe/PipeMulti.js,https://InFrontOfF5.com/APE_JSF/Source/Pipe/PipeSingle.js,https://InFrontOfF5.com/APE_JSF/Source/Request/Request.js,https://InFrontOfF5.com/APE_JSF/Source/Request/Request.Stack.js,https://InFrontOfF5.com/APE_JSF/Source/Request/Request.CycledStack.js,https://InFrontOfF5.com/APE_JSF/Source/Transport/Transport.longPolling.js,https://InFrontOfF5.com/APE_JSF/Source/Transport/Transport.SSE.js,https://InFrontOfF5.com/APE_JSF/Source/Transport/Transport.XHRStreaming.js,https://InFrontOfF5.com/APE_JSF/Source/Transport/Transport.JSONP.js,https://InFrontOfF5.com/APE_JSF/Source/Transport/Transport.WebSocket.js,https://InFrontOfF5.com/APE_JSF/Source/Core/Utility.js,https://InFrontOfF5.com/APE_JSF/Source/Core/JSON.js > baseUrl : https://InFrontOfF5.com/APE_JSF > domain : InFrontOfF5.com > server : ApeInFrontOfF5.com.com:443 > secure : true > Running test : Setting document.domain > Running test : Checking APE.Config.baseUrl > APE JSF Version 1.0 > Running test : Contacting APE Server > Can't contact APE Server. Please check the your APE Server is running > and the folowing url is pointing to your APE server : > https://ApeInFrontOfF5.com.com:443 > Something went wrong. If you can't fix it by yourself post a message > on the newsgroups with the output below or join our IRC channel > > > Any ideas what to try next ? The F5 load balancer will push encrypted > ApeInFrontOfF5.com.com:443 traffic unencrypted to behindF5.com:81 > > Brgrds, Chris > > -- > You received this message because you are subscribed to the Google > Groups "APE Project" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/ape-project?hl=en > --- > APE Project (Ajax Push Engine) > Official website : http://www.ape-project.org/ > Git Hub : http://github.com/APE-Project/ > -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
