Strcat(srv_xdata->ISTag, ISTAG "-XXXXXXXXX\"") Īfterward, I was able to connect my cluster to the /echo service. Strcat(srv_xdata->ISTag, ISTAG "-XXXXXXXXX") ISTag: "3A30802306E6FCA2416679010E77FAE1"Īs a test, I updated the following 2 lines in the service.c file and recompiled 2) Select profile in urlcheck service using acls icapheader acl to check the X-Authenticated-Groups ICAP header. In looking at the output from c-icap, the output is not quoted, which is different than the products that are working and would seem to be a deviation from the RFC3507 spec. You have two options: 1) Pass the username to the ICAP Service using the X-Authenticated-User header and then use the GroupSourceByUser c-icap configuration option to define the groups into c-icap. It appears the c-icap is not adhering to the RFC3507 for the ISTag output. Information from the pcaps may be helpful as well as debug informationįrom the c-icap server to see if that reports anything specific. Of and ensure it has appropriate data back. Recommend looking at the c-icap documentation.īoast compatibility with RFC 3507 compliant ICAP servers, there is stillĭata that OneFS needs in order to understand what the server is capable Looking at the c-icap project documentation Response, OneFS doesn't alter the ICAP server status to online seeing itĬan't process the header. Seeing some of the application data is missing from the c-icap 100 const struct icap_header_string icap_hdr =
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |