帮助 - >停止发布数据到期？ [英] HELP -> stop post data expiring?
问题描述
对不起，这不是一个交叉帖子..我只是没有从alt.php得到任何帮助。
我有一个网站，利用邮政表格在某些地区进行导航。 />
问题是，当*某些*用户按下BACK按钮时，POSTDATA
内容已过期，他们需要刷新页面然后他们得到一个
关于刷新过期数据的提醒。
我收到投诉，这太烦人了，限制了网站
的可用性。
出于安全原因，我无法交换帖子以获取。
页面的标题内容是
header（''Expires：''。。gmdate （''D，d MYH：我：s''，时间（）+ 600）。''GMT''）;
似乎适用于某些浏览器/系统但是不是其他人......
我想覆盖用户缓存设置，但我不确定这个
如何才能最好地实现POST数据
非常感谢任何帮助。
brendan写道：
对不起，这不是一个交叉的帖子..我只是没有从alt.php得到任何帮助。
我有一个网站，在某些地区使用帖子表格进行导航。
问题是，当*某些*用户按下BACK按钮时，POSTDATA
内容已过期，他们需要刷新页面然后他们会收到关于刷新过期数据的警报。
我抱怨这太烦人了，限制了网站的可用性。
安全原因我不能交换帖子获取。
页面的标题内容是
标题（''过期：''。。gmdate（''D，d MYH：i：s' '，time（）+ 600）。''GMT''）;
这似乎适用于某些浏览器/系统但不适用于其他浏览器/系统......
我想要覆盖用户缓存设置但不确定如何在POST数据方面最好地实现这一点
任何帮助都非常感激。
嗨布兰登，
我不确定你能修这个。
AFAIK有些浏览器告诉访问者他们看到的页面是
发布（表单）的结果。这是一件好事，因为它是
发布的结果。
我不确定你是否可以通过添加标题来解决这个问题..（希望对你有帮助） />
有人知道。:-)
如果你想修复这种行为，你可以添加自己的
导航按钮到页面并实现一个体面的帖子''返回'' - 按钮
行为。虽然这并不总是可行的。
老实说，我不明白你用的安全实现
GET通过POST消失了。
POST数据也是通过网络发送的，它只是没有显示在URL中，
但它就在那里.....
如果您想要更高的安全性，请使用加密。 （https）
只需2美分。
问候，
Erwin Moller
Erwin Moller写道：
brendan写道：
对不起，这不是一个交叉的帖子..我只是没有得到alt.php的任何帮助。
我有一个网站，利用帖子表格在某些地区进行导航。
问题是，当*某些*用户点击后按钮POSTDATA
内容已经过期，他们需要刷新页面，然后他们会收到关于刷新过期数据的警报。
我收到投诉，这太烦人了网站
可用性。
出于安全考虑，我无法交换帖子获取。
页面的标题内容是
标题（''Expires ：''。。gmdate（''D，d MYH：我：s''，时间（）+ 600）。''GMT''）;
这似乎适用于某些浏览器/系统但不是其他人......
我想过度骑车用户缓存设置，但不确定如何最好地实现POST数据
任何帮助非常感谢。
你好brendan ，
我不确定你是否可以修复它。
AFAIK一些浏览器告诉访问者他们看到的页面是
发布（表单）的结果。这是一件好事，因为它是发布的结果。
我不确定你是否可以通过添加标题来解决这个问题..（希望对你来说
有人知道。:-)
如果你想修复这种行为，可以在页面上添加自己的
导航按钮，并为后退实现一个不错的帖子 - 按钮
行为。虽然这并不总是可行的。
老实说，我不明白你使用POST消失的安全实现。
POST数据也会发送在网络上，它只是没有显示在URL中，
但它就在那里.....
如果你想要更高的安全性，请使用加密。 （https）
只是我的2美分。
问候，
Erwin Moller
谢谢Erwin ，
问题是使用
二进制哈希来加入几个字符串参数，这可能导致某些字符串参数比某些字符串更长。 b $ b浏览器允许的GET字符串长度。由于没有MIME控件
GET，我无法想到一个解决方法。我错了吗？
我不确定禁用浏览器按钮或使用无铬窗口
会吸引用户的焦虑而不是需要刷新。
关于https的权利：它只是我们的网络服务器使用了一些真正的
lame DN（即 https://www.yourreallysecurenow.com 等）我们希望保留
产品徽标......猜测我们可以使用框架...但是当用户刷新任何东西时，这会导致另外一组问题。
感谢您的回复，但是...知道我不是唯一一个
左右。
欢呼
brendan。
brendan写道：
Erwin Moller写道：
brendan写道：
对不起，这不是一个交叉的帖子..我只是没有得到任何帮助fr om alt.php。
我有一个网站，利用帖子表格在某些地区进行导航。
问题是，当*某些*用户按下BACK按钮时，POSTDATA
内容已经过期，他们需要刷新页面，然后他们会收到关于刷新过期数据的警报。
我抱怨这太烦人了，限制了网站的可用性。
出于安全考虑，我无法更换帖子以获取。
页面的标题内容是
标题（''过期：''。。gmdate（'' D，d MYH：i：s''，time（）+ 600）。''GMT''）;
这似乎适用于某些浏览器/系统，但不适用于其他浏览器/系统...
我想覆盖用户缓存设置，但我不确定如何在POST数据方面最好地实现这一点
任何帮助都非常感激。
你好brendan，
我不确定你可以修这个。
AFAIK有些浏览器告诉访问者他们看到的页面是一个结果
波斯蒂ng（表格）。这是一件好事，因为它是发布的结果。
我不确定你是否可以通过添加标题来解决这个问题..（希望对你来说
有人知道。:-)
如果你想修复这种行为，你可以在页面上添加自己的
导航按钮，并为
''返回''实现一个不错的帖子 - 按钮行为。虽然这并不总是可行的。
老实说，我不明白你使用POST消失的GET安全实现。
POST数据也发送通过网络，它只是没有显示在
URL中，但它就在那里.....
如果你想要更高的安全性，请使用加密。 （https）
只是我的2美分。
问候，
Erwin Moller
感谢Erwin，
嗨再次，
问题是使用
二进制哈希对几个字符串参数进行了加密，这可能导致某些字符串参数长于一些
浏览器允许GET字符串长度。
哦，这还有问题吗？
我认为这对（非常老的）webSERVERS来说只是一个问题。
在这种情况下你应该坚持POST。
:-(
由于没有MIME控件来获取GET，我无法想到一个解决方法。我错了吗？
对不起，我不知道POST有MIME控制。我认为它是一堆
的名字/值对具有特定编码，没有MIME AFAIK。
很可能我错了。：P
也许有人知道更多关于这可以澄清一下吗？
我不确定禁用浏览器按钮或使用无边框窗口
会吸引用户的焦虑，而不是需要刷新。
嗯。好的。
如果您在发布一些formdata后收到来自网络服务器的回复，那么
只有在您使用时浏览器会发出警告才符合逻辑你的后退按钮。至少
很有意义对我来说。
作为旁注：
我认为问题是很多人使用浏览器（你的客户）是
不知道这一点，并且不知道发布的是什么，没有b $ b的线索过期意味着什么，最重要的是：不要我也想学习它。
（根据自己的经验说）。
所以，除非你能以某种方式解决这个浏览器行为，否则你应该教育
你的用户这实际上是互联网浏览器所希望的行为。
就像有人在他生命中第一次踏入汽车，开始
驾驶，并得到他崩溃后生气，因为喘息的工作与他预期的不同。他只需要一个驱车。
但这对你没有帮助，是吗？ ;-)
关于https的权利：它只是我们的网络服务器使用了一些非常蹩脚的DN（即 https://www.yourreallysecurenow.com 等）我们想保留
产品徽标...猜我们可以使用框架...但是这会导致<当用户刷新任何东西时，另一组问题。
感谢您的回复......很高兴知道我不是唯一一个
周围。
欢呼/> brendan。
如果记忆能很好地为我服务M
Sorry this isnt a cross post .. i just didnt get any help from alt.php.
I have a website which utilises post forms for navigation in some areas.
Problem is, when *some* users hit the BACK button the POSTDATA
content has expired and they need to refresh the page then they get a
alert about refreshing expired data.
I am getting complaints that this is too annoying and limits the sites
useability.
For security reasons I cant swap post for get.
the header content of the page is
header(''Expires: ''.gmdate(''D, d M Y H:i:s'', time() + 600) .''GMT'');
which seems to work on some browsers/systems but not others ...
I want to over-ride the users cache settings but am not sure how this
can be best achieved in respect of POST data
any help greatly appreciated.
brendan wrote:
Sorry this isnt a cross post .. i just didnt get any help from alt.php.
I have a website which utilises post forms for navigation in some areas.
Problem is, when *some* users hit the BACK button the POSTDATA
content has expired and they need to refresh the page then they get a
alert about refreshing expired data.
I am getting complaints that this is too annoying and limits the sites
useability.
For security reasons I cant swap post for get.
the header content of the page is
header(''Expires: ''.gmdate(''D, d M Y H:i:s'', time() + 600) .''GMT'');
which seems to work on some browsers/systems but not others ...
I want to over-ride the users cache settings but am not sure how this
can be best achieved in respect of POST data
any help greatly appreciated.
Hi brendan,
I am not sure you can repair this.
AFAIK some browsers tell the visitor that the page they see is a result of a
posting (form). Which is a good thing, because it is the result of a
posting.
I am unsure if you can fix this by adding headers.. (hopefully for you
somebody knows. :-)
If you want to ''repair'' this behaviour, you can add your own
navigationbuttons to the page and implement a decent post for ''back''-button
behaviour. Allthough this is not always possible.
And honestly I don''t understand the security-implementations you have with
GET that disappear by using POST.
POST data is also send over the network, it just doesn''t show up in the URL,
but it is there.....
If you want more security, use encryption. (https)
just my 2 cents.
Regards,
Erwin Moller
Erwin Moller wrote:
brendan wrote:Sorry this isnt a cross post .. i just didnt get any help from alt.php.
I have a website which utilises post forms for navigation in some areas.
Problem is, when *some* users hit the BACK button the POSTDATA
content has expired and they need to refresh the page then they get a
alert about refreshing expired data.
I am getting complaints that this is too annoying and limits the sites
useability.
For security reasons I cant swap post for get.
the header content of the page is
header(''Expires: ''.gmdate(''D, d M Y H:i:s'', time() + 600) .''GMT'');
which seems to work on some browsers/systems but not others ...
I want to over-ride the users cache settings but am not sure how this
can be best achieved in respect of POST data
any help greatly appreciated.
Hi brendan,
I am not sure you can repair this.
AFAIK some browsers tell the visitor that the page they see is a result of a
posting (form). Which is a good thing, because it is the result of a
posting.
I am unsure if you can fix this by adding headers.. (hopefully for you
somebody knows. :-)
If you want to ''repair'' this behaviour, you can add your own
navigationbuttons to the page and implement a decent post for ''back''-button
behaviour. Allthough this is not always possible.
And honestly I don''t understand the security-implementations you have with
GET that disappear by using POST.
POST data is also send over the network, it just doesn''t show up in the URL,
but it is there.....
If you want more security, use encryption. (https)
just my 2 cents.
Regards,
Erwin Moller
Thanks Erwin,
the problem is that several string parameters are enrcypted using a
binary hash and this can result in some being longer than some of
browsers permissable GET string length. As there is no MIME control for
GET there I cant think of a workaround. Am I wrong on this one?
I am not sure that disabling browser buttons or using chromeless windows
would attract any less angst from users than the need to refresh.
your right about https: its just that our webserver uses some really
lame DN (ie https://www.yourreallysecurenow.com etc) and we want to keep
the product logo ... guess we could use frames ... but that causes
another set of problems when users refresh anything.
thanks for your response though ... its good to know Im not the only one
around.
cheers
brendan.
brendan wrote:
Erwin Moller wrote:brendan wrote:Sorry this isnt a cross post .. i just didnt get any help from alt.php.
I have a website which utilises post forms for navigation in some areas.
Problem is, when *some* users hit the BACK button the POSTDATA
content has expired and they need to refresh the page then they get a
alert about refreshing expired data.
I am getting complaints that this is too annoying and limits the sites
useability.
For security reasons I cant swap post for get.
the header content of the page is
header(''Expires: ''.gmdate(''D, d M Y H:i:s'', time() + 600) .''GMT'');
which seems to work on some browsers/systems but not others ...
I want to over-ride the users cache settings but am not sure how this
can be best achieved in respect of POST data
any help greatly appreciated.
Hi brendan,
I am not sure you can repair this.
AFAIK some browsers tell the visitor that the page they see is a result
of a posting (form). Which is a good thing, because it is the result of a
posting.
I am unsure if you can fix this by adding headers.. (hopefully for you
somebody knows. :-)
If you want to ''repair'' this behaviour, you can add your own
navigationbuttons to the page and implement a decent post for
''back''-button behaviour. Allthough this is not always possible.
And honestly I don''t understand the security-implementations you have
with GET that disappear by using POST.
POST data is also send over the network, it just doesn''t show up in the
URL, but it is there.....
If you want more security, use encryption. (https)
just my 2 cents.
Regards,
Erwin Moller
Thanks Erwin,
Hi again,
the problem is that several string parameters are enrcypted using a
binary hash and this can result in some being longer than some of
browsers permissable GET string length.
Oh, is that still a problem?
I thought that was only a problem for (very old) webSERVERS.
In that case you should stick to POST indeed.
:-(
As there is no MIME control for
GET there I cant think of a workaround. Am I wrong on this one?
Sorry, I wasn''t aware that POST had MIME-control. I think of it as a bunch
of name/value pairs with a certain encoding, no MIME AFAIK.
Very well possible I am wrong on that one. :P
Maybe somebody who knows more about this can clarify this??
I am not sure that disabling browser buttons or using chromeless windows
would attract any less angst from users than the need to refresh.
Hmm. ok.
If you get a response from a webserver after posting some formdata, it is
only logical that a browser warns you if you use your back-button. At least
that makes a lot of sense to me.
As a sidenote:
I think the problem is that many people using a browser (your customers) are
not aware of that, and don''t have a clue what a posting is, don''t have a
clue what ''expired'' means, and above all: don''t want to learn it either.
(Speaking from own experience).
So unless you can fix this browser-behaviour somehow, you should educate
your users that this is actually desired behaviour of an internetbrowser.
It is like somebody steps into a car for the first time in his life, starts
driving, and gets angry after he crashes because the gaspedal worked
differently than he ''expected''. He simply needs a driverlicence.
But that doesn''t help you, does it? ;-)
your right about https: its just that our webserver uses some really
lame DN (ie https://www.yourreallysecurenow.com etc) and we want to keep
the product logo ... guess we could use frames ... but that causes
another set of problems when users refresh anything.
thanks for your response though ... its good to know Im not the only one
around.
cheers
brendan.
If memory serves me well M
这篇关于帮助 - >停止发布数据到期？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
