I read the following from the blueprints website about not allowing the user to use non-SSL requests after an SSL request has been processed.
"If you are using sessions, once you switch to SSL
you should never accept any further requests for that session that are non-SSL. For example, a shopping site might not use SSL until the checkout page, then it may switch to using SSL in order to accept your card number. After switching to SSL, you should stop listening to non-SSL requests for this session. The reason for this practice is that the session ID itself was non-encrypted on the earlier communications, which is not so bad when you're just doing your shopping, but once the credit card information is stored in the session, you don't want a bad guy trying to fake the purchase transaction against your credit card. This practice could be easily implemented using a filter."
I understand Sun's reasoning to not allow non-SSL after an SSL call is made.
But if I do what is recommended above, Change Itinerary process which requires the user to be logged-in (using SSL) may not be able to call Prepare Itinerary (which is a non-SSL process until we get to payment).
How are situations like this handled in the real-world?
Solomon