On 15/05/07, Kostadin Cholakov <[EMAIL PROTECTED]> wrote: > > Hi > > We are using the development server only! Can you give me some > reference for the necessary changes in the code? Thanks! > > On 5/15/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > > On Tue, 2007-05-15 at 19:14 +0000, Kostadin Cholakov wrote: > > > Hello, > > > > > > We are currently using Django for access to a linguistic database > > > where people can validate certain entries by checking certain > > > checkboxes! We have the problem that the users are not in our > > > departament and they are connected to Internet through a different > > > proxy server. When the annotators check boxes and go to the next page > > > and then again go back, the boxes are not checked anymore. We tried to > > > reproduce this error with different browsers but we were not able to > > > do this! So, we susspect that their server caches some pages and when > > > the annotators go back to a previous page, it doesn't invoke GET to > > > get a fresh page with the updated entries and checkboxes but rather > > > their server takes the original cached page! We would like to see > > > which machine exactly accesses our database and see what kind of > > > request it makes... But the log files just show the URL which is being > > > used, the time and POST or GET... Is there any way that one could > > > retrieve more information like IP for example? I am new to Django and > > > I was not able to find something on this issue! Thanks! > > > > It depends on what web server you are using. Every web server has ways > > to configure what information is logged. > > > > If you are just using the development server, then you're out of luck > > without changing the code. > > > > Regards, > > Malcolm > >
If this application is not going to be very limited use, in-house only, with no more than 1 person making requests at a time, then you'd better consider hosting it in a proper environment. Where proper is anything to your liking, except the development server. If people are going to use this thing, you'll run in a lot more issues than the current one you're having. I'd say that catching up with the documentation about deployment, instead of applying duct-tape patches will result in a lot less trouble for you. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
