Cannot add attachments
We have been unable to add attachments to feature services behind the Geocortex Identity Server since upgrading to GE 4.0 and HTML5 2.2.
GE 4.0 and HTML5 2.2 gives a 'bad request' error. HTTP 400 Bad Request in Fiddler. We upgraded our test box to GE 4.2 with HTML5 2.3 to see if that would fix it, but that gives an internal server error (nothing shows in Fiddler at all, as if it is not even trying to upload anything).
Disabling site security allows us to add attachments with HTML5 2.2, but disabling security with HTML5 2.3 still results in an Internal Server Error.
Is there some setting within Identity Server or with GE Manager to allow adding attachments with security enabled?
Has anyone else experienced this since upgrading?
-
Has anyone else experienced this? I am inclined to think this is a bug in the software. Any from Latitude available for comment?
0 -
This is still an issue with GVH 2.3.2 and GE 4.2.1
Fiddler shows the post url as having the token added twice. Maybe that has something to do with it?
From Fiddler, returns HTTP 400 Bad Request:
POST http://<our domain>/Geocortex/Essentials/REST/sites/<site name>/map/mapservices/7/MapServer/657/addattachment?token=<token value>&token=<token value> HTTP/1.1
0 -
Anyone resolve this issue?
Im having the same issue on my end
0 -
Hi folks,
I can confirm that this is a bug on our end -- two bugs, in fact. The one issue is, as Dan indicates, a problem with submitting the token twice; the other is that the proxy did not properly support POSTs of multipart data to the addattachment endpoint. We've fixed this issue on the Essentials side of things in 4.2.2 (GE-6176 & GE-6184) and on the viewer side, we will have a fix in HTML5 Viewer 2.4, available later this month (GVH-4704).
I apologize for the inconvenience this has caused you in the meantime.
Jordan
0 -
Hi Jordan,
I am getting a Bad Request error when adding attachments to a secure feature service in GE 4.5.1, GVH 2.6.1.
Do you know if the above fix was implemented?
Thanks
Dave0 -
Hmm... Looking back through the code, it appears that the fix was reverted after 2.4. I've asked the viewer team to investigate. I'll follow up shortly. 0 -
Looks like I was mistaken: the QA team has taken a look at the fix, and it's working as intended for them in the 2.4 viewer and beyond.
Dave, would you mind opening a case with the (To: support@latitudegeo.com) Support team so we can take a look at your setup and maybe get a Fiddler capture of the request and the error? It's possible that you've encountered an edge case we've missed or even a different issue with similar symptoms.0
Please sign in to leave a comment.
Comments
7 comments