Hi friends, does anyone know how to properly edit httpd.conf in 14.1? Mine keeps reverting on reboot and I need to edit out a few lines to fix a DUO issue.

Have you set up rc.netscaler? That should help you to replace the original file after reboot with the customized one.

rc.netscaler?

You don't need to put it there. Bind those to the Gateway portal along with the AAA portal and it will work.

No, but might help https://support.citrix.com/s/article/CTX206613-on-netscaler-making-changes-to-rcnetscaler-does-not-persist-reboot?language=en_US

ok maybe thats why. I bound only to AAA

@Jeff Riechers has a point, no need to modify files

hmmm. still getting error

Are they bound as Rewrite-Response? Also you may have to clear the integrated cache as well.

Should they be bound as reqrite response or AAA response?

Response, not AAA response

just undbound and rebind them again. Same error..

Make sure to invalidate the cache, since some of this can get cached.

I dont have cache feature enabled. does it still work?

Yup, those are correct. Check your developer tools to see if those headers are still showing up.

Ok I flushed the cache and that did it...

Yes, flush is the better option, it will get rid of all the stale data right away. And has no effect on users using the system.

is anything cached on user browsers too?

This is just cache in the NS engine, not local cache.

ah ok. I remember with certain changes to netscaler interface there was user cache involved too

I did this with a large environment, putting this in and hitting invalidate mid day didn't impact anyone.

this is what I did

In the pic I showed above, go there and hit invalidate all, then just say ok.

ah ok. I missed that part.

There is an option to disable the cache altogether. Go to Security —> AAA, then edit the global settings/parameters. There should be a setting “disable static cache”, which should solve your issue.

@Jan Tytgat Would that cause any issues down the road?

Negative, the only difference is that the apache process on the NetScaler will have to handle each request that asks for a file normally served by the webserver, instead of the NetScaler Packet engine. So as long as your NetScaler isn’t under heavy load, no issue at all.