Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I am getting "302 Found" error while saving an article. I have also got the PHP version updated to 5.3.13. but the problem is still there.
The full description of error is shown in attached file.
| Comment | File | Size | Author |
|---|---|---|---|
| admin-error-save.png | 81.49 KB | pragna |
Comments
Comment #1
Alan Evans CreditAttribution: Alan Evans commentedThis doesn't look like it belongs in the core issue queue, at a glance it's a server configuration issue, which is not a bug in drupal core, but rather a support request.
I'm downgrading this for the time being as the critical status generates unnecessary noise.
I will check D7.12 right now and see if I can "save an article", which is all you have provided by way of steps to reproduce your issue. If I am unable to reproduce the issue (which seems highly likely, given how many people in the world will have been succesfully saving articles since 7.12), then this will need to be recategorized as a support request (or closed as can-not-reproduce) until we have some evidence of a fault in the code. If I can reproduce the issue, then we can always push back up to critical later.
You can help me by providing detailed steps to reproduce your issue including as much detail as you can. Show me how I can walk through what you have done and come out with the same error. More detail is better. Details of server configuration and setup would be a good idea.
What the "302 Found" error means is that the server has been set up in such a way that when an error occurs (which may be something simple like a 404), it is supposed to look for a specified document. That document itself caused a temporary redirect to happen (which isn't a good idea)
Comment #2
Alan Evans CreditAttribution: Alan Evans commentedI was unable to reproduce the issue as described on 7.12: https://skitch.com/e-alanevans/eb6jb/test-testd712.localhost.
Reclassifying as a support request - if you can provide detailed steps to reproduce which prove an issue in code, this can be moved back into the bug queue again.
As a support request, you'll probably need to provide a more descriptive title in order to get attention on the issue as well as more details of the setup steps that led to this happening.
It might be worth asking in #drupal-support http://drupal.org/irc
Comment #3
Alan Evans CreditAttribution: Alan Evans commentedNote that the Link: header in your screenshot implies to me that the node was actually saved, but that the response coming back from the server was garbage.
What I see at a glance from your screenshot is that there is a potentially correct response in there (beginning HTTP/1.1 200 OK ), but that the error document message precedes the "good" response, which is not allowed - you have output here before the headers.
Your first thing to check is your nginx / varnish configuration.
The "O" character preceding the first