wood burning stoves 2.0*
The moose likes JSP and the fly likes Passing Http headers to a different domain. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Java » JSP
Bookmark "Passing Http headers to a different domain." Watch "Passing Http headers to a different domain." New topic
Author

Passing Http headers to a different domain.

Surendra Babu
Greenhorn

Joined: Jun 19, 2007
Posts: 2
Hi All,
Thank you for such a wonderful forum. Here is my question

Want to pass info from site1c.com to site2.com :
------------------------------------------------
(user) --> site1.com (for authentication) --> site2.com (for content browsing)

I have a website called site1.com,
which authenticates the user package the user info (userid, email) and encrypt into a variable.
Now I need to pass this (encrypted string) information to another site site2.com (completely different domain, a third party site). site2.com know how to decrypt and validate the token information.

Trying to pass though HTTP Header, but Failed:
-----------------------------------------------
I have been thinking of passing this variable (Token) through HTTP Headers (as a HTTP header variable). But, I wasn't able to do this. I used this code:
response.addHeader("MS-TOKEN", "testing token value");
response.sendRedirect("site2.com/index.jsp");

I can see the header variables getting to browser, but they are missing into "site2.com" request from the browser. (I used Charles to see the request/response info.)

Any other Ideas, please:
-------------------------
My sites (source, target) being in two different domains, I think we're having few options.
Can you pls. suggest other alternatives? which one of the following is better one?
Browser Redirect with GET parameters -- users can see the parameters, but its encrypted anyway.
Browser redirect with POST parameters -- using java script to auto submit the form information to site2.com. if JS is disabled, it may fail to auto submit.
Cookie -- since these two are different domains, cookie may not be passed between the domains (i.e., setting cooke from site1.com and passing it to site2.com).

Thanks
Surendra.
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12769
    
    5
Browser Redirect with GET parameters -- users can see the parameters, but its encrypted anyway.


Thats the most reliable way as far as I know. You will need to program some additional mechanism to ensure that the URL can not be used again.

Bill
Surendra Babu
Greenhorn

Joined: Jun 19, 2007
Posts: 2
Thank you Bill.

Yes, we're making sure that token gets invalidated after a specific time. We're including the time stamp into the token. When data is decrypted, If the time stamp is more than acceptable threshold, token gets invalidate user is sent back for login.
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61106
    
  66

"asb tech", please check your private messages for an important administrative matter.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
Karthik Rajendiran
Ranch Hand

Joined: Aug 13, 2004
Posts: 211
Hello Friend,

Sending data as query parameters to the application is fine.
Only thing is your encryption logic should be known to that application to decrypt it.


SCJP 1.4 SCWCD 1.4 SCDJWS 1.4
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Passing Http headers to a different domain.