Fabio wrote: > Hi, > > I'm evaluating Trac (and it really tops my expectations), but a > strange error is causing a poor user experience: most of the pages > fails into HTTP 303 response after submitting changes. Although this > bad effect, the updates become effective.
303 is not a failure code, but a redirect. Trac uses the "POST-redirect-GET" idiom, which is good practice in web applications [1]. This can lead to, as with any other redirects, some issues with getting the protocol and host right, hence the discussion about use_base_url_for_redirect in the ticket 7060. > It is similar to bugs > reported in > > http://trac.edgewall.org/ticket/8583 > > and in > > http://trac.edgewall.org/ticket/7060 > > > Scenario description: > - Trac 0.11.5 installation > - tracd is serving the project > - user has TRAC_ADMIN permission > - tracd web front-end fails after submitting data (HTTP 303 is > displayed at server console window) > That's expected so far. > - It's necessary to use back and refresh buttons to view changes > become effective. > Which browser are you using? Chances are this is IE7. > - tracd IS NOT behind a proxy > > > Any insights on how to fix it? > Use the --http11 option when running tracd. Besides fixing your problem (likely the http://trac.edgewall.org/ticket/8020 one), you'll also get a nice performance boost ;-) -- Christian [1] http://en.wikipedia.org/wiki/Post/Redirect/Get --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
