Can't get request caching to work in dockerized container
See original GitHub issueConfirm you’ve already contributed to this project or that you sponsor it
- I confirm I’m a sponsor or a contributor
Version
3.x
Question
I have an OpenIddict identity server that works fine when deployed as an azure app service, but if i try to deploy it as a dockerized container and validate using it (through B2C) i get an error that ‘The specified ‘request_id’ is invalid’. The url that it’s using is something like https://|my site|/connect/authorize?request_id=KloxbYfo4KZ7n-I7UBB7jfCK0KEsMHhqiqcUJkiZY1s
I don’t see any errors, and the only logs i see from the server are:
2022-02-12T16:01:12.947404065Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The request address matched a server endpoint: Configuration.","State":{"Message":"The request address matched a server endpoint: Configuration.","Endpoint":"Configuration","{OriginalFormat}":"The request address matched a server endpoint: {Endpoint}."}}
2022-02-12T16:01:12.948095274Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The configuration request was successfully extracted: {}.","State":{"Message":"The configuration request was successfully extracted: {}.","Request":"{}","{OriginalFormat}":"The configuration request was successfully extracted: {Request}."}}
2022-02-12T16:01:12.949852198Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The configuration request was successfully validated.","State":{"Message":"The configuration request was successfully validated.","{OriginalFormat}":"The configuration request was successfully validated."}}
2022-02-12T16:01:12.966884823Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The response was successfully returned as a JSON document: ....
2022-02-12T16:01:13.247721845Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The request address matched a server endpoint: Cryptography.","State":{"Message":"The request address matched a server endpoint: Cryptography.","Endpoint":"Cryptography","{OriginalFormat}":"The request address matched a server endpoint: {Endpoint}."}}
2022-02-12T16:01:13.263200650Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The cryptography request was successfully extracted: {}.","State":{"Message":"The cryptography request was successfully extracted: {}.","Request":"{}","{OriginalFormat}":"The cryptography request was successfully extracted: {Request}."}}
2022-02-12T16:01:13.271657862Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The cryptography request was successfully validated.","State":{"Message":"The cryptography request was successfully validated.","{OriginalFormat}":"The cryptography request was successfully validated."}}
2022-02-12T16:01:13.355147869Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The response was successfully returned as a JSON document: ....
2022-02-12T16:01:13.549556945Z {"EventId":0,"LogLevel":"Information","Category":"OpenIddict.Server.OpenIddictServerDispatcher","Message":"The request address matched a server endpoint: Authorization.","State":{"Message":"The request address matched a server endpoint: Authorization.","Endpoint":"Authorization","{OriginalFormat}":"The request address matched a server endpoint: {Endpoint}."}}
which don’t seem like they show any issues at all. Any ideas on where i should be looking to fix this issue? The dockerfile is just:
FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
EXPOSE 80
EXPOSE 8081
COPY bin/Release/net6/ App/
WORKDIR /App
ENTRYPOINT ["dotnet", "IdentityManager.dll"]
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (8 by maintainers)
Top Results From Across the Web
Unable to get --cache-from to work - docker
I ran into this problem where only the final image is available for caching. Depending on the steps you run, this can appear...
Read more >Image-building best practices
Summary. In this section, you learned a few image building best practices, including layer caching and multi-stage builds. Related information:
Read more >API Caching with Redis, Flask, and Docker [Step-By-Step]
For this tutorial we're going to use Redis, to save the responses from the API, and then use those responses instead of making...
Read more >Speed up pip downloads in Docker with BuildKit's new caching
The first time we run this, Docker will of course have to run pip install from scratch, and pip will download Flask and...
Read more >10 things to avoid in docker containers | Red Hat Developer
10 things to avoid in docker containers · "Containers are ephemeral". · 1) Don't store data in containers · 2) Don't ship your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yep, that was it thank you. Instead of redis, for now i just reduced the instance count to 1 and everything worked. Thank you!
Then I’m out of ideas 😄 Did you try to lower the log level to Debug/Trace to see if there’s anything interesting?
I’ll try to reproduce that on my end when I have a moment.