I have created a SharePoint 2010 site that is accessible both internally and externally. I have created alternate access mappings for https://<internal_url> (Extranet) and https://<external_url> (Internet). Requests, however, only come to the internal_url as there is a reverse proxy which translates the addresses.
This setup generally works fine as SharePoint uses relative URLs for most things. However, I'm experienceexperiencing some problematic bits, with the most annoying one being the following error after file upload, when Edit Properties form should be shown:
No item exists at https://**<internal_path>**/Forms/EditForm.aspx?Mode=Upload&CheckInComment=&ID=5&RootFolder=/<path>&IsDlg=1. It may have been deleted or renamed by another user.
Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.
Troubleshoot issues with Microsoft SharePoint Foundation.
Note that the upload is successful but the Edit Properties popup window shows this error (the background is still there). It's not a critical issue but I know the user base, they are not very technical and we'll be facing constant support calls and lack of confidence in the solution.
Obviously, the confirmation tries to open the site at the internal URL (by which it has been requested any way, after the domain name translation at the reverse proxy), which is naturally unavailable externally.
I get this error only when Web Client service is started - when it's not in the same popup I get "Internet Explorer Cannot Open the Webpage" (although the logs may show the same error)
I'm also getting the same error when creating lists and document libraries, and similar situation with datasheet view for lists - the client tries to connect to the server by the internal URL and naturally fails.
CanAt first I make this work properly without messing with the general architecture ofthought that it's caused by the DMZ infrastructure, which uses a reverse proxy - which, I thought, translates the address to the internal URL and the rest of the site works purely because SharePoint uses relative URLs. This seems not to be the case, as we did some tracing on the proxy and it in fact translates the external address to the IP address - and it doesn't show anywhere in error messages. I don't know how definitive this is as I have no idea about the tools that sysadmins use and how reliable they are - but the admins seem pretty confident. But if that's try then it seems that SharePoint is sending the internal URL to client via some other mechanism.
Any ideas how can I make this work? Or at least what's going on?
Update: Multiple upload works wellFurther, the problem presents itself for libraries that either have check-in/check-out enabled or have multiple content types - so an acceptable workaroundothers simply don't show the popup. For some libraries on the site, however, multiple content types is a part of the requirements. A valid workaround would be a way to make thisprevent the default optionEdit Form popup being shown after upload to a library with multiple content types.