Almost everytime I submit a form in the web front end then go look at the data I changed, it is not "changed." If I resfresh that page, it will then show the changed value. Seems as though PHP or the browser is caching the original value.
For example: I change a template item's Update Interval from 60 to 300. Save. View that item again (not using the back button, but by clicking on the item again). Although I did submit/save the form, it will show 60 still in the Update Interval field. At this point, I refresh the page, then it changes it to the value that was saved (300).
It seems to clearly to be a cached form field value. I've been using the latest versions of Safari and Firefox on OS X. Both with the same behavior.
My question is if anyone has a pointer for me as to what setting to change to prevent this behavior... something global in my php.ini? Or is this something to edit in the php files themselves? Assuming it's something that can be addressed by setting Cache-Control headers, is this something that others have to deal with? Maybe it's something in the default php.ini on OS X that other platforms do not turn on by default.
Zabbix Server 1.8.5 on Mac OS X Server 10.6.7 (Darwin Kernel 10.7.0)
Web frontend 1.8.5
2x Quad-Core Intel Xeon 3 GHz
Apache/2.2.17 & PHP/5.3.4
For example: I change a template item's Update Interval from 60 to 300. Save. View that item again (not using the back button, but by clicking on the item again). Although I did submit/save the form, it will show 60 still in the Update Interval field. At this point, I refresh the page, then it changes it to the value that was saved (300).
It seems to clearly to be a cached form field value. I've been using the latest versions of Safari and Firefox on OS X. Both with the same behavior.
My question is if anyone has a pointer for me as to what setting to change to prevent this behavior... something global in my php.ini? Or is this something to edit in the php files themselves? Assuming it's something that can be addressed by setting Cache-Control headers, is this something that others have to deal with? Maybe it's something in the default php.ini on OS X that other platforms do not turn on by default.
Zabbix Server 1.8.5 on Mac OS X Server 10.6.7 (Darwin Kernel 10.7.0)
Web frontend 1.8.5
2x Quad-Core Intel Xeon 3 GHz
Apache/2.2.17 & PHP/5.3.4