On Mon, Feb 22, 2010 at 9:01 PM, Morten Omholt Alver <mortenal...@gmail.com> wrote: > I don't know all that much about talking to HTTP servers, so I may be > making some basic mistake. If there is anyone knowledgeable that would > be willing to help out with the HTTP stuff, it would probably increase > the chances of getting the JStor fetcher operational again.
I cannot find the tool I used a long time ago, but it is often helpful, to use a proxy tool you just use for JabRef calling the JStor server, and dump the traffic... that will give you all HTTP headers, including the cookie information... Now, I don't remember what tool I used in the past, but any will do, I guess... google is too noisy for me to find something simple... Egon -- Post-doc @ Uppsala University Proteochemometrics / Bioclipse Group of Prof. Jarl Wikberg Homepage: http://egonw.github.com/ Blog: http://chem-bla-ics.blogspot.com/ PubList: http://www.citeulike.org/user/egonw/tag/papers ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Jabref-devel mailing list Jabref-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jabref-devel
