dd4t/dd4t.restservice.webapi

The DD4T RestService

dd4t.restservice.webapi's Issues

Is DD4T 2.1.0 is compatible with .NETCoreApp 2.0?

We are getting the following warning when using DD4t resrService.WebApi with .NETCore 2.0

{
"code": "NU1701",
"level": "Warning",
"warningLevel": 1,
"message": "Package 'DD4T.Core 2.1.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This package may not be fully compatible with your project.",
"libraryId": "DD4T.Core",
"targetGraphs": [
".NETCoreApp,Version=v2.0"
]
},

Element 'httpRuntime' is duplicated in Web.config

The code that modifies the Web.config does not work properly: it leaves a few duplicate elements (httpRuntime I believe and another, related one).
@sshibani can you please check this some time?

remove dependency on log4net so that we can use logging framework of our choice

We are using Serilog across our application stack except with our DD4T restservice as it is dependent on log4net please consider removing this dependency and instead be able to pass through logger of choice

Debug Mode

If debug mode is enabled, decompress and unzip the published data.

possible solution:

• add key to web.config to enable the functionality.
• add additional routes

if debug is set to true, decompress and unzip the data.

Support for Sites9

Hi Guys,

I have made a version of the DD4T.RestService.WebApi that supports Sites9 and upgraded the .Net Framework to 4.6.2... (I kinda needed that version haha).

If you want to; I made a branch /feature/upgrade-sites9 and hope you can check whether it's okay or not? And hopefully use it to update this project?

Kind regards,
Kaan

PublicationId 0 (zero) is not supported over REST

In the native Tridion pageproviders, it is possible to set the publication id to 0. This means: get the page by URL without looking at the publication id. This works fine in many implementations, especially if the publicationUrl property is unique per publication.

In the REST provider an error is thrown if the publication id is 0. Please make the behaviour consistent (by allowing 0 for the REST provider).