I just got burned by this on my own site, losing a forum post that took
me a while to write. How hard would it be to fix this issue, it really
sucks to lose the user's (read: my) data.
Chris
--
Open source business p
I would think the current post could be stuffed into the post_error.html
page (or its replacement) when it's generated, then carried across to
the login page, and then reposted, so it wouldn't require javascript at
all. I haven't thought about it too much, though.
It's just a terrible user exp
On 2014-07-09, 15:11, Chris Hecker wrote:
> I just got burned by this on my own site, losing a forum post that took
> me a while to write. How hard would it be to fix this issue, it really
> sucks to lose the user's (read: my) data.
The easy solution is to use a browser add-on such as Lazarus tha
On 2014-07-09, 16:23, Chris Hecker wrote:
> I would think the current post could be stuffed into the post_error.html
> page (or its replacement) when it's generated, then carried across to
> the login page, and then reposted, so it wouldn't require javascript at
> all. I haven't thought about it to
I think the payload size is probably not an issue in the vast majority
of the use cases, so a simple cosign setting for the max size of all the
post variables would be sufficient. But yes, it would require some thought.
Chris
On 2014-07-09 13:39, Mark Montague wrote:
> On 2014-07-09, 16:23,
I've wondering if the additions to httpd 2.4 that support mod_auth_form
could be leveraged by mod_cosign.
http://httpd.apache.org/docs/2.4/mod/mod_auth_form.html
One specific part of that is "Inline Login with Body Preservation"
http://httpd.apache.org/docs/2.4/mod/mod_auth_form.html#i
I wonder if I could do a cheesy workaround for my site that would use
javascript to hook the post button on the forum page, and then test for
expired credentials, and then pop up a login box if they are, then
resume the post. It's a hack, but it might work.
Chris
On 2014-07-09 13:10, Mark Mo
On 2014-07-09, 16:24, Chris Hecker wrote:
> I wonder if I could do a cheesy workaround for my site that would use
> javascript to hook the post button on the forum page, and then test for
> expired credentials, and then pop up a login box if they are, then
> resume the post. It's a hack, but it mi
Chris Hecker writes:
> I just got burned by this on my own site, losing a forum post that took
> me a while to write. How hard would it be to fix this issue, it really
> sucks to lose the user's (read: my) data.
My long-term plan for WebAuth, which has the same problem for the same
reasons, was
