something that I noticed while testing hte mod_proxy config, when you are trying to use the samples that come with flex, you are unable to view the source code for the samples because there is an httpservice error.
I also would like to see a working config with mod_jk. After the 6-7 times trying to get it to work, I was never able to get it working properly. --- charlespaz1 <[EMAIL PROTECTED]> wrote: > Would you be willing to share your mod_jk > configuration? Everything > I've found has been either out of date or so grossly > inaccurate to be > useless. > > I realize that all requests to Tomcat through > mod_proxy are > indentified as coming from the proxy server, > however, for my current > development process, that is acceptable. Eventually > I'd like to get > mod_jk working, but that's a priority issue, and it > isn't one right now. > > --- In [email protected], "Eric Raymond" > <[EMAIL PROTECTED]> wrote: > > While I strongly recommend the use of Apache as a > front end for Tomcat > > in production, the use of mod_jk and mod_proxy > have some interesting > > implications with respect to Flex. In my > experience, Macromedia was > > not helpful in resolving these issues. > > > > IMHO, mod_jk is much better than mod_proxy. It's > a shame the > > documentation is so obscure ... but I think it is > better now than it > > used to be. > > > > If you use mod_proxy, realize that anytime you try > to reference the > > users IP address, you will be getting the address > of the proxy server, > > not the user. By the time the request gets > through the flex proxy > > (not mod_proxy) to your servlet, the orignal info > is gone. In many > > cases you really want to know where your customers > are coming from. > > The way around this is to create a servlet filter > that saves the > > original ip address before the flex proxy so that > you can later > > retrieve it after the flex proxy hands the request > to your service. > > (Confusing eh? There are two proxies here: the > apache mod_proxy and > > the tomcat flex proxy). > > > > I believe there were some strange interactions > between mod_proxy and > > ssl. One that comes to mind is that the flex > server thinks it is > > dealing with http so it generates an html mxml > wrapper that references > > things via http. This causes clients to get the > "some of the > > information on this page is insecure" message. > > > > Now mod_jk has had problems with the flex proxy. > Your mileage may > > vary: > > > http://www.mail-archive.com/[email protected]/msg05870.html > > > > It's been a while but I think there may have been > some other issues > > with HttpSevices (but I'm not sure on this). > We've worked around all > > of them, but we did have to deal with them > unexpectedly. Surely > > others must have run into these roadblocks as > well. Perhaps few are > > using the combination of tools we use: apache, > mod_jk, tomcat, ssl, > > httpservice, custom authentication, etc. I've > always reported these > > to customer service and logged them as bugs, so > perhaps they will be > > addressed in a future version of Flex. Then > again, these types of > > bugs so easily fall in a sea of finger pointing, > non-trivial test case > > setups, and passing the buck. > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------ Yahoo! Groups Sponsor --------------------~--> Fair play? Video games influencing politics. Click and talk back! http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
