> >> Hi mongoose-users, >> This is an announcement of 5.0 release. > [snip] > >> protect_uri (not useful) > > [snip] >> >> Updated documentation is at http://cesanta.com/#docs >> >> Happy New Year, >> Sergey. >> > > Hmmm - interesting that this option as seen as not useful! I find that one > of my applications (using version 3.1) makes good use of it by having a > URI specific to writing data to an application that is protected but other > URIs that read only are 'in the free'. > > Would it be possible to patch back from a late version 4 or has the > internal structure changed too much? > > I like the single thread approach now being used (simplifies embedding a > lot not having to use a pthread library) but the loss of this feature > could stop me upgrading.
Well I've tried with a .htpasswd file and that basically stops everything in its tracks for reading static files, and doesn't help for URIs that go directly via a handler (i.e. there is no directory to store the file in as the embedded app serves up via the callback). A lot of changes to the code in this area from what I see, basically the auth stuff is not applied to the callback code at all any more :( I can see that the protect_uri code wasn't helpful for the stand-alone executable but for embedded use with callbacks it was really neat! Does the DAV or PUT auth help me at all? If so, how do I drive it? Cheers -- Robin Gilks -- You received this message because you are subscribed to the Google Groups "mongoose-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mongoose-users. For more options, visit https://groups.google.com/groups/opt_out.
