Even before this last mail, my suggestion would have been trying without firebug. I have hit a different problem (http:// code.google.com/p/fbug/issues/detail?id=650) which I'm sure is firebug (it is generating an extra HTTP request, rather than failing to submit one). All I've been able to think of doing is put a note on the page that it might not work correctly with firefox/firebug: since this is an internal website, not many users are likely to have fb.
On Jul 4, 12:41 pm, SImonJ <[EMAIL PROTECTED]> wrote: > OK, quick update, I downloaded a HTTP monitor plugin for firefox and > discovered that although the request was being created, it wasn't > being completely sent - and would get stuck at something 1100/1198 or > something (the numbers changed slightly every time). > > Anyway, I saw that this was working when logged on at a different > terminal, so I decided to try running the page with no firebug and no > http monitor plugin and it worked first time (and fortunately every > time after that). > > Has anyone seen this sort of thing before? It's a bit of a pain to be > honest as there's every chance that some of the intended users of the > site might be using these sort of plugins... > > Simon > > On Jul 4, 9:47 am, "Gareth Evans" <[EMAIL PROTECTED]> wrote: > > > Have you got a web debugging proxy? It might be time to dig one out and see > > if you can investigate the request and response and see if it's reaching the > > server at all. > > I use Fiddler, but that's windows. > > > Gareth > > > On Fri, Jul 4, 2008 at 8:41 PM, SImonJ <[EMAIL PROTECTED]> wrote: > > > > OK, so I tested the idea of putting a random number on the end of the > > > url but to no avail. > > > > More weirdness to this issue is that it appears to work as expected > > > under Firefox 3 on my Ubuntu laptop, but not under firefox 2 on my > > > Solaris terminal at work... Starts to make me think there is a problem > > > with the JS, however the request appears just as expected in the > > > firebug console, but it's just not hitting the PHP file. > > > > Anyone have any ideas at all as I'm starting to lose the will to live > > > on this one :S > > > > Thanks - Simon > > > > The problem > > > > On Jul 3, 3:54 pm, "Frederick Polgardy" <[EMAIL PROTECTED]> wrote: > > > > Shouldn't matter if these are POST's though, browsers aren't allowed to > > > > cache POST requests. > > > > > -Fred > > > > > On Thu, Jul 3, 2008 at 9:39 AM, Ryan Gahl <[EMAIL PROTECTED]> wrote: > > > > > To get started, we can test the caching theory pretty easily. When you > > > are > > > > > building your request, append "?###" where ### is a randomly generated > > > > > token... therefore making each request to a unique endpoint. > > > > > -- > > > > Science answers questions; philosophy questions answers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
