Unset Last-Modified header for Form Runner Pages

Hi All,

I'm trying to not set the Last-Modified header for form runner, since having
the server return a 304 Not Modified response is interfering with FORM based
login when an unauthenticated request is made to the server.

I've modified the oxf.http.page.cache-headers to set the Last-Modified
header to 0 as follows

/<property as="xs:string"  name="oxf.http.page.cache-headers">
    Cache-Control: private, max-age=0; Last-Modified: 0; Pragma:
</property>/

Is there any adverse side effect in doing this?

Kind regards
Kris

--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Kris,

I am not sure about possible adverse effects, but I'd be interested in
understanding what the issue you're trying to solve is. If authentication is
required, and users haven't logged in yet or the session expired, Orbeon
Forms shouldn't respond with a 304 Not Modified, in the sense that the
request shouldn't even get to Orbeon Forms? What am I missing?

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Alex,

In our case When users leave a form open in the form runner and their
session then expired, they will be presented with the following (in browsers
other than IE11 per my other question):
  <http://discuss.orbeon.com/file/t375253/Selection_001.png>

When they then click ok it will trigger the reload of the form (a request to
fr/<app name>/<form name>/edit/<form ID> containing an If-Modified-Since
request header). The server then responds with a 304 Not Modifed for this
request. This results in our login page not being presented to the user.

Kind regards
Kris

--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Kris,

Interesting. Do you know "who" answers with the 304? I imagine the Orbeon
Forms could, but if users needs to login, the request shouldn't get to
Orbeon Forms, and it is instead whoever handles the login before the request
gets to Orbeon Forms that should serve the login page. Or are you saying
that it is this code that serves the login page that answers the request
with a `If-Modified-Since` with a "304 Not Modified"? In which case, if I
may ask, what are you using to serve the login page?

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Kris, do you still have this issue? If so, do you know who is answering
with a 304 (also see my previous message on this)? -Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].