Sending a HTTP POST request

Sending a HTTP POST request

To implement single sign off, i would like the user to get logged out of application B additionally when ever the user clicks logout on application A. Is it possible to implement this using some form of a POST request to application B? i.e. when the user clicks on logout:

  1. Generate existing POST request to logout of application A
  2. Generate additional POST request to logout of application B as well.

How to keep link alive on mongoose web server


C++ Concurrent GET requests
The cleanest way to do this is to check if your SSO provider has a single-sign-off feature.

When to send HTTP status code?
HTTP 400 : detected invalid characters in the URL. IIS decoding URL too early? Whats going on here?
Coding this up and deploying it would make your overall IT solution a bit brittle.

How to send an HTTP header in java
How to specify an external website for XMLHTTPRequest
Another suggestion is to take this up with your (Enterprise) architect as SSO is usually an enterprise initiative and point her to (very cogent) arguments in this post : .
Why is curl sending the command-line before the message body in an HTTP PUT?

What C++ library should I use to implement a HTTP client? [closed]


Yes, how you do it depends on the programming language you are using.. For example under ASP.Net you'd use System.Net.HttpWebRequest within the handling of the Logout event of application A to make a logout request to application B. If you can post what language you're working in I can give a proper example.


Depending on the implementation of your authentication system, probably you can/need to send the POST using JavaScript instead of from server-side..


Without specific information, it's hard to give a specific answer, but as you're refering to POST, I'll assume a browser is involved.. POSTs (without using Javascript or similar) occur when a form is submitted.

As the form can have only one action, it can only target one server-side page.. One solution is to simply have Application A forward sign-out credentials to Application B once one action is received, which allows for more opportunities to check returns.. If, however, you're set on POST'ing to different pages, see this tutorial for one iframe-related hack -


If your login session is stored by a cookie, and there are nothing else you need to supply to log out of application B, clearing the cookie in javascript will usually destroy the session and sign the user out..


How about making it a cookie based authentication? A same cookie authenticates a user for various applications (in your case 2 different application.) Once a user sign off from one application (app A), invalidates a cookie (by expiry date) so that whenever a user sends a POST request to rest of the application (app B) the request is not processed.

A Servlet that traces each POST request to validate the cookie is required for each application..

85 out of 100 based on 55 user ratings 655 reviews