Skip to content
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
This repository was archived by the owner on Nov 22, 2024. It is now read-only.

Http Breaks On Server Side When Using Windows Auth #750

@yanbu0

Description

@yanbu0

Note: for support questions, please use one of these channels: https://github.com/angular/universal/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports. Also, Preboot has moved to https://github.com/angular/preboot - please make preboot-related issues there.

  • I'm submitting a ...
- [ x] bug report
- [ ] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.
  • What modules are related to this Issue?
- [x ] aspnetcore-engine
- [ ] express-engine
- [ ] hapi-engine
  • Do you want to request a feature or report a bug?

Report a bug

  • What is the current behavior?

Does not work with Windows Authentication and Web API.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem by creating a github repo.

Get the "offical" ASP.NET CORE repo from https://github.com/MarkPieszak/aspnetcore-angular2-universal, enable windows authentication. Navigate to the /users route. Note in the console Node gets 401 errors, but the code fails over to getting the data from a browser side query.

  • What is the expected behavior?

Node is able to get data from Web API with windows auth enabled.

  • What is the motivation / use case for changing the behavior?

Windows Auth is really useful when developing internal business applications and pretty widely supported.

  • Please tell us about your environment:
  • Angular version: 4.2.4
  • Browser: [all ]
  • Language: [TypeScript 2.3.4 ]
  • OS: [ Windows ]
  • Platform: [NodeJs | .NETCore y]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

I originally thought this was an issue with the transferHttp functionality in the asp.net core repo, but it occurs using a straight Angular http.get() call as well.

More details here: TrilonIO/aspnetcore-angular-universal#112

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions