Back Midas Rome Roody Rootana
  Midas DAQ System, Page 7 of 138  Not logged in ELOG logo
New entries since:Wed Dec 31 16:00:00 1969
ID Date Authordown Topic Subject Text Attachments
  1100   21 Aug 2015 Thomas LindnerInfomhttpd HTTPS/SSL server updated
> I recommend that you use "mhttpd --mg"
as the alternative for running "mhttpd -p"
  
  1107   09 Sep 2015 Thomas LindnerInfomhttpd HTTPS/SSL server updated> > 
> > I find that I don't understand this recommendation
to use secure mongoose 
  
  1108   09 Sep 2015 Thomas LindnerInfomhttpd/SSL error message on MacOSOn my macbook (OS X 10.10.3) I get this error
message when starting mhttpd with mongoose-SSL:
  
  1109   09 Sep 2015 Thomas LindnerInfoDocumentation regarding specifying custom pagesHi,

We have recently been changing the code in
  
  1159   05 Feb 2016 Thomas LindnerSuggestionreducing sleep time in mhttpd main loop (for sequencer)There were some complaints that the MIDAS
sequencer was slow.  Specifically, the
complaint was that even lines in the sequence
  
  1160   05 Feb 2016 Thomas LindnerSuggestionreducing sleep time in mhttpd main loop (for sequencer)> There were some complaints that the MIDAS
sequencer was slow.  Specifically, the
> complaint was that even lines in the sequence
  
  1162   15 Feb 2016 Thomas LindnerSuggestionreducing sleep time in mhttpd main loop (for sequencer)
> > I checked how much extra CPU was used
if the sleep was reduced from 100ms to
  
  1169   10 Mar 2016 Thomas LindnerInfoNew rootana forum | rootana web display tools
We have started a new elog for discussions
of the ROOTANA MIDAS analyzer package
  
  1177   11 May 2016 Thomas LindnerInfoMacOS 10.11 (El Capitan) openssl compilation errorsI recently upgraded my macbook to MacOS 10.11.
 The compilation of MIDAS failed after the
upgrade, 
  
  1217   25 Oct 2016 Thomas LindnerBug Reportcontrol characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail> > I've recently run into issues when using
JSON.parse on ODB keys containing 
> > 8-bit data.
  
  Draft   04 Nov 2016 Thomas LindnerBug Reportproblem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinksHi Tim,

I reproduced your problem and then managed
  
  1220   04 Nov 2016 Thomas LindnerBug Reportproblem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinksHi Tim,

I reproduced your problem and then managed
  
  1221   25 Nov 2016 Thomas LindnerBug Reportproblem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinksThe procedure I wrote seemed to work for Tim
too, so I added a page to the wiki about
it here:
  
  1223   01 Dec 2016 Thomas LindnerBug Reportcontrol characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail> > I've recently run into issues when using
JSON.parse on ODB keys containing 
> > 8-bit data.
 odb_modifications.txt 
  1224   05 Dec 2016 Thomas LindnerInfoJavascript based run start and stop pages.> I switched mhttpd to use the new javascript
based run start and stop pages.
  
  1227   15 Jan 2017 Thomas LindnerBug Reportcontrol characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail> > In other words, non-UTF-8 strings are
following non-IEEE-754 floating point values
into oblivion - as 
  
  1228   23 Jan 2017 Thomas LindnerBug Reportcontrol characters not sanitized by json_write - can cause JSON.parse of mhttpd result to fail
> At Konstantin's suggestion, I committed
the function I found for checking if a string
  
  1251   16 Mar 2017 Thomas LindnerBug ReportReplaced with /experiment/menu, mhttpd - /Experiment/Menu Buttons - git-sha a350e8db11> > > I think there sneaked in a little bug
in the mhttpd: when starting an experiment
> > > from scratch and starting the mhttpd,
  
  1290   04 May 2017 Thomas LindnerForumMIDAS Workshop - July 26Dear MIDAS users,

We would like to announce another MIDAS workshop
  
  1301   19 Jun 2017 Thomas LindnerBug Reportmhttpd ODB editor changes string length, breaks I guess this might be related to the changes
in the last elog conversation; but
I'll break it out as a separate problem.
  
ELOG V3.1.4-2e1708b5