Railgun - URL Only, or Session Aware? (HTTP request Headers, Cookies, ETags, etc)

I am considering using the Railgun app for my website. However my website may return very different responses for the same URL depending on HTTP request Headers that control session information.

Is it possible to set up Railgun to be “session aware” based on HTTP Headers, or something like ETags? Or does all identifying data for the request need to be present in the URL?

Just using the URL it seems that if 2 users were accessing the same URL with different sessions that Railgun would be thrashing between the two having to constantly send most of the data on each request. Is there a recommended method to handle this type of setup?

This topic was automatically closed after 14 days. New replies are no longer allowed.