Evergreen ILS Website

IRC log for #evergreen, 2016-01-18

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
00:19 dcook joined #evergreen
05:01 rlefaive joined #evergreen
06:40 rlefaive joined #evergreen
07:21 rlefaive joined #evergreen
07:33 mrpeters joined #evergreen
07:56 collum joined #evergreen
08:17 ericar joined #evergreen
08:29 rlefaive joined #evergreen
09:28 mrpeters anyone out there force https for all of their traffic to TPAC?  what is the preferred method?  .htaccess?  modification to the eg.conf?
09:36 maryj joined #evergreen
09:51 miker yes, and however your shop agrees to and documents for all there to know. (though, why you'd use a .htaccess for something global and static, I couldn't guess...)
09:55 mrpeters miker: i wasn't suggesting .htaccess was the ultimate way to go, just a possible way.  i've been checking around some of the bigger catalogs and it doesn't look like most are using HTTPS so we may just secure the quick-reports app individually
10:03 mrpeters miker: what would you propose as an alternative to .htaccess, considering mod_rewrite is already in use?
10:04 mrpeters seems like a RewriteCond for a particular directory would be appropriate
10:04 mrpeters is it your opinion that using eg_vhost.conf for that is more appropriate?
10:07 * mrpeters just noticed the # Uncomment the following to force SSL for everything. Note that this defeats caching # and you will suffer a performance hit. notes in eg_vhost.conf
10:31 miker mrpeters: for "force https for all of their traffic to TPAC", yes, it's my opinion that the main config, not .htaccess, is more appropriate. if you are actually talking about something other than "all TPAC traffic" then that changes the discussion.  That's not the same as the global setting you alluded to, though.
10:31 mrpeters miker: yeah, i went with the model used for selfcheck
10:32 mrpeters i was just curious if anyone was doing it globally
10:32 miker however, in any case, I prefer pretty much anything to .htaccess unless you're planning to allow outside parties access and control
10:32 mrpeters fair enough
10:33 miker because that's the purpose of .htaccess (different levels of access authorization and control for specific paths within a document root) whether it can be used for other things or not.
11:09 Christineb joined #evergreen
11:20 collum joined #evergreen
11:29 dbs One note: forcing HTTPS for everything does block uploads of offline transactions
11:32 dbs I always have to remember to disable "force HTTPS" after we have some down time to allow for the offline uploads
12:11 jihpringle joined #evergreen
12:12 jeffdavis All our EG traffic goes through a load balancer, which forces SSL (with exceptions for a couple places where that doesn't work) and handles cert stuff.
16:43 Bmagic when coping the var/web/updates directory - which files exactly do you neeed for the staff client to smoothly upgrade itself? just the archive directory?
16:44 Bmagic I copied the whole updates tree and I ended up with "malformed xml" error
16:46 Bmagic more detail - I'm installing evergren on a fresh machine but I want it to have the upgrade path for the currently installed staff client so that my staff client will upgrade itself on the fresh machine
17:26 dcook joined #evergreen
17:47 mrpeters left #evergreen
18:20 artunit joined #evergreen
18:45 eady joined #evergreen
20:48 bshum Bmagic: my recollection was archives was the only one we needed.
20:48 bshum But admittedly it's been a couple years since the last time we had to change things up.
20:54 jihpringle joined #evergreen
22:50 Christineb joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat