This is a placeholder issue assigned to no project. It has been raised to track issues that have been raised with the SSP via the DDC. Each issue will be updated as and when updates are available
1) SSP is not persisting headers returned from Provider systems that contain caching headers
Expected Result
When responding to GPConnect API intercations, if the Provider system includes caching headers i.e. ‘Cache-Control: no-store’ in the response then the SSP should not perform any validation on this header. However the following error is produced.
Having checked the outputs returned from EMIS, they are definitely returning it so the SSP is stripping this out
Timeline
Raised with Conrad at the DDC via e-mail 12/12/17
09/01/18 - after discussion with Amit he will also escalate to DDC
2) SSP is not persisting headers returned from Provider systems that contain etag headers
Expected Result
For Read requests and Read, Update and Create Reponses GPConnect interactions etag headers may be produced by the relevant servers however the SSP should not SSP should not perform any validation on this header. However the following error is produced.
Having checked the outputs returned from EMIS, they are definitely returning it so the SSP is stripping this out
Timeline
Raised with Conrad at the DDC via e-mail 12/12/17
09/01/18 - after discussion with Amit he will also escalate to DDC
This is a placeholder issue assigned to no project. It has been raised to track issues that have been raised with the SSP via the DDC. Each issue will be updated as and when updates are available
1) SSP is not persisting headers returned from Provider systems that contain caching headers
Expected Result When responding to GPConnect API intercations, if the Provider system includes caching headers i.e. ‘Cache-Control: no-store’ in the response then the SSP should not perform any validation on this header. However the following error is produced. Having checked the outputs returned from EMIS, they are definitely returning it so the SSP is stripping this out Timeline Raised with Conrad at the DDC via e-mail 12/12/17 09/01/18 - after discussion with Amit he will also escalate to DDC
2) SSP is not persisting headers returned from Provider systems that contain etag headers
Expected Result For Read requests and Read, Update and Create Reponses GPConnect interactions etag headers may be produced by the relevant servers however the SSP should not SSP should not perform any validation on this header. However the following error is produced. Having checked the outputs returned from EMIS, they are definitely returning it so the SSP is stripping this out Timeline Raised with Conrad at the DDC via e-mail 12/12/17 09/01/18 - after discussion with Amit he will also escalate to DDC