You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to make an HTTP call using the TaskQueue API, the operation fails on CapeDwarf due to a missing mandatory "Host" HTTP header. This issue does not occur on Google App Engine (GAE) SDK, indicating a specific problem with CapeDwarf's handling of HTTP headers in TaskQueue operations.
Error Message
Couldn't find the mandatory "Host" HTTP header.
This is followed by a NullPointerException in ServletCall.java:370.
Code Snippet
The error occurs when executing a basic TaskQueue operation:
A workaround involving an HTTP filter to manually set the "Host" header was attempted, but it led to further runtime errors and instability within the CapeDwarf environment.
Environment
CapeDwarf version: 2.0.0.Final
Expected Behavior
TaskQueue operations should include all mandatory HTTP headers, including "Host", without requiring manual intervention or workarounds.
Actual Behavior
The "Host" header is missing in TaskQueue operations, leading to failed HTTP requests and errors in the application log.
Steps to Reproduce
Set up a basic TaskQueue operation as shown in the code snippet.
Deploy the application to CapeDwarf.
Observe the error in the application logs after the TaskQueue operation is executed.
Additional Context
This issue does not occur on other platforms like GAE Legacy Cloud Runtime or AppScale, suggesting a problem with CapeDwarf's TaskQueue implementation.
The text was updated successfully, but these errors were encountered:
Description
When attempting to make an HTTP call using the TaskQueue API, the operation fails on CapeDwarf due to a missing mandatory "Host" HTTP header. This issue does not occur on Google App Engine (GAE) SDK, indicating a specific problem with CapeDwarf's handling of HTTP headers in TaskQueue operations.
Error Message
This is followed by a
NullPointerException
inServletCall.java:370
.Code Snippet
The error occurs when executing a basic TaskQueue operation:
Workaround Attempt
A workaround involving an HTTP filter to manually set the "Host" header was attempted, but it led to further runtime errors and instability within the CapeDwarf environment.
Environment
Expected Behavior
TaskQueue operations should include all mandatory HTTP headers, including "Host", without requiring manual intervention or workarounds.
Actual Behavior
The "Host" header is missing in TaskQueue operations, leading to failed HTTP requests and errors in the application log.
Steps to Reproduce
Additional Context
This issue does not occur on other platforms like GAE Legacy Cloud Runtime or AppScale, suggesting a problem with CapeDwarf's TaskQueue implementation.
The text was updated successfully, but these errors were encountered: