Appreciate all the input! Those things were already part of my list that are mentioned in this email. What I was trying to point was that we are really in restrictive env where server A can't be changed and 3rd party may not agree to change. So I was wondering if there is something like caching on Apache servers or something similar that can help. So if user A with id "A" comes to site 1 and if that user is actually supposed to be in site 2 then redirect. Or may be some better solution on similar lines. On Wed, Mar 30, 2011 at 7:11 AM, Ben Timby <btimby@xxxxxxxxx> wrote: > On Wed, Mar 30, 2011 at 12:12 AM, Mohit Anchlia <mohitanchlia@xxxxxxxxx> wrote: >> thanks! F5 supports the cookies and is recommended way but the problem >> is server A is not managed by us and may be very difficult to >> convience them to enter cookie (changing code). Is it possible to >> embed cookies for non-browser clients in serverA? > > I don't understand the question. Server A is an HTTP client, so it > would have a chance to inject cookies. They are after all just an HTTP > header. Whether it is a browser or not is irrelevant. > >> Are there any other options if server A can't be changed. > > Not with the little information I have. If I was working on this > solution, the major part of the project would be research. Traffic > dumps between client and server A, traffic dumps between server A and > my system. Code review of server A. How? Why? What? Who? When? Where? > If there is a needle there, you need to find it, otherwise, you will > need to find the smallest impact method for embedding a needle. Either > way, information is key and research is the way of gathering > information. The implementation is always simpler than the discovery, > otherwise the project is boring. > > I think we have given about all the available solutions to you, but > your job is to find the details needed to implement them. We can't do > that for you. > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|