This question is locked. New answers and comments are not allowed.
When pulling from a remote repository over http (http://server/git/repo) i get the the error (http://server/git/repo: 417 Expectation Failed).
When doing the same from git commandline, everything works fine.
When doing the same from git commandline, everything works fine.
3 Answers, 1 is accepted
0
Hi Marc,
What if you try a pull over https instead? Does your git provider lists support for http? Also are you trying this from the browser (AppBuilder in-browser) or from the AppBuilder Windows client? Any additional information you could provide would be appreciated.
Regards,
Steve
Telerik
What if you try a pull over https instead? Does your git provider lists support for http? Also are you trying this from the browser (AppBuilder in-browser) or from the AppBuilder Windows client? Any additional information you could provide would be appreciated.
Regards,
Steve
Telerik
Check out the new Telerik Platform - the only modular platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native apps. Register for the free online keynote and webinar to learn more about the Platform on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT).
0
Marc
Top achievements
Rank 1
Rank 1
answered on 31 Jan 2014, 08:35 AM
> Also are you trying this from the browser (AppBuilder in-browser) or from the AppBuilder Windows client?
The error messages in the in-browser client and the windows client are the same.
> Does your git provider lists support for http
We are hosting git on on of our own servers (which supports smart HTTP transport)
> What if you try a pull over https instead?
Since it seems not possible to accept self signed certificated when pushing or pulling over HTTPS, i could not try this yet.
Anyway it seems that i've found the actual problem, which is an incopatibility between the jgit client on teleriks server and lighttpd on our server. These are the headers of the HTTP-Request:
Request:
---------------
POST /git/mobile/git-upload-pack HTTP/1.1
Accept-Encoding: gzip
Pragma: no-cache
User-Agent: JGit/2.1.0.0
Authorization: [REMOVED]
Content-Type: application/x-git-upload-pack-request
Accept: application/x-git-upload-pack-result
Content-Encoding: gzip
Host: [REMOVED]
Content-Length: 161
Expect: 100-continue
Reply:
---------------
HTTP/1.1 417 Expectation Failed
Content-Type: text/html
Content-Length: 363
Connection: close
Date: Fri, 31 Jan 2014 08:21:48 GMT
Server: lighttpd/1.4.34
Sending "Expect: 100-continue" is not supported by the stable versions (1.4.x) of lighttpd.
The error messages in the in-browser client and the windows client are the same.
> Does your git provider lists support for http
We are hosting git on on of our own servers (which supports smart HTTP transport)
> What if you try a pull over https instead?
Since it seems not possible to accept self signed certificated when pushing or pulling over HTTPS, i could not try this yet.
Anyway it seems that i've found the actual problem, which is an incopatibility between the jgit client on teleriks server and lighttpd on our server. These are the headers of the HTTP-Request:
Request:
---------------
POST /git/mobile/git-upload-pack HTTP/1.1
Accept-Encoding: gzip
Pragma: no-cache
User-Agent: JGit/2.1.0.0
Authorization: [REMOVED]
Content-Type: application/x-git-upload-pack-request
Accept: application/x-git-upload-pack-result
Content-Encoding: gzip
Host: [REMOVED]
Content-Length: 161
Expect: 100-continue
Reply:
---------------
HTTP/1.1 417 Expectation Failed
Content-Type: text/html
Content-Length: 363
Connection: close
Date: Fri, 31 Jan 2014 08:21:48 GMT
Server: lighttpd/1.4.34
Sending "Expect: 100-continue" is not supported by the stable versions (1.4.x) of lighttpd.
0
Hi Marc,
Thank you for the thorough reply and additional details you have provided. As we're using a port of JGit that does not have a newer version and you are the first one to report such an issue, we would have to say that there isn't anything we can do about this problem at this time. It does sound like a limitation of the web server you're using, so if it is important to have this functionality working, we would suggest migrating to a server that does not have such problem.
Regards,
Steve
Telerik
Thank you for the thorough reply and additional details you have provided. As we're using a port of JGit that does not have a newer version and you are the first one to report such an issue, we would have to say that there isn't anything we can do about this problem at this time. It does sound like a limitation of the web server you're using, so if it is important to have this functionality working, we would suggest migrating to a server that does not have such problem.
Regards,
Steve
Telerik
Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)