You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by depuys <de...@imsweb.com> on 2008/07/07 19:04:35 UTC

Commit problems with certain file types using https:// URLs

Hello,

I'm attempting to configure Subversion so all user access is via Apache and
https:// URLs.  Converting CVS repositories and creating new ones has gone
well.  However, the problem we're having is committing certain file types. 
Extensions txt, png, gif, and jpg are problematic.  Extensions cfg, sas,
bin, html, java, xml, asdf, c, asc, and tiff are fine.  The errors look like
this.

svn: Commit failed (details follow):
svn: CHECKOUT of
'/svn/seerdms/!svn/ver/34186/seerdms/trunk/conf/cp/test_file.txt': 501
Method Not Implemented (https://intranet2.imsweb.com)

Transmitting file data ....svn: Commit failed (details follow):
svn: PUT of
'/svn/bsi/!svn/wrk/0f708b16-414b-11dd-8177-cd479e07ddbe/bsiweb/trunk/static/images/kryo_back.png':
405 Method Not Allowed (https://intranet2.imsweb.com)

Everything works fine using file:// access.  The Apache error logs don't
report any problems.  The return codes 405 and 501 can be seen in the Apache
access logs but nothing helpful is there.  I've looked at the Apache mime
types and can't find a correlation between these types.  I've also looked at
~/.subverison/config and can't gain any insight into the issue.

Thanks,
Scott

-- 
View this message in context: http://www.nabble.com/Commit-problems-with-certain-file-types-using-https%3A---URLs-tp18324214p18324214.html
Sent from the Subversion Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Commit problems with certain file types using https:// URLs

Posted by depuys <de...@imsweb.com>.
No, there isn't a Web proxy involved in these communications.  These errors
were generated from using an svn client from the Linux command line
communicating directly with Apache.  There isn't any server side caching
going on for any files.


Ryan Schmidt-42 wrote:
> 
> On Jul 7, 2008, at 14:04, depuys wrote:
> 
>> I'm attempting to configure Subversion so all user access is via  
>> Apache and
>> https:// URLs.  Converting CVS repositories and creating new ones  
>> has gone
>> well.  However, the problem we're having is committing certain file  
>> types.
>> Extensions txt, png, gif, and jpg are problematic.  Extensions cfg,  
>> sas,
>> bin, html, java, xml, asdf, c, asc, and tiff are fine.  The errors  
>> look like
>> this.
>>
>> svn: Commit failed (details follow):
>> svn: CHECKOUT of
>> '/svn/seerdms/!svn/ver/34186/seerdms/trunk/conf/cp/test_file.txt': 501
>> Method Not Implemented (https://intranet2.imsweb.com)
>>
>> Transmitting file data ....svn: Commit failed (details follow):
>> svn: PUT of
>> '/svn/bsi/!svn/wrk/0f708b16-414b-11dd-8177-cd479e07ddbe/bsiweb/ 
>> trunk/static/images/kryo_back.png':
>> 405 Method Not Allowed (https://intranet2.imsweb.com)
>>
>> Everything works fine using file:// access.  The Apache error logs  
>> don't
>> report any problems.  The return codes 405 and 501 can be seen in  
>> the Apache
>> access logs but nothing helpful is there.  I've looked at the  
>> Apache mime
>> types and can't find a correlation between these types.  I've also  
>> looked at
>> ~/.subverison/config and can't gain any insight into the issue.
> 
> Do you have a proxy server of some kind that's getting in the way?
> 
> Do you have some kind of caching going on at the Apache level for  
> files of those extensions?
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Commit-problems-with-certain-file-types-using-https%3A---URLs-tp18324214p18335285.html
Sent from the Subversion Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Commit problems with certain file types using https:// URLs

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jul 7, 2008, at 14:04, depuys wrote:

> I'm attempting to configure Subversion so all user access is via  
> Apache and
> https:// URLs.  Converting CVS repositories and creating new ones  
> has gone
> well.  However, the problem we're having is committing certain file  
> types.
> Extensions txt, png, gif, and jpg are problematic.  Extensions cfg,  
> sas,
> bin, html, java, xml, asdf, c, asc, and tiff are fine.  The errors  
> look like
> this.
>
> svn: Commit failed (details follow):
> svn: CHECKOUT of
> '/svn/seerdms/!svn/ver/34186/seerdms/trunk/conf/cp/test_file.txt': 501
> Method Not Implemented (https://intranet2.imsweb.com)
>
> Transmitting file data ....svn: Commit failed (details follow):
> svn: PUT of
> '/svn/bsi/!svn/wrk/0f708b16-414b-11dd-8177-cd479e07ddbe/bsiweb/ 
> trunk/static/images/kryo_back.png':
> 405 Method Not Allowed (https://intranet2.imsweb.com)
>
> Everything works fine using file:// access.  The Apache error logs  
> don't
> report any problems.  The return codes 405 and 501 can be seen in  
> the Apache
> access logs but nothing helpful is there.  I've looked at the  
> Apache mime
> types and can't find a correlation between these types.  I've also  
> looked at
> ~/.subverison/config and can't gain any insight into the issue.

Do you have a proxy server of some kind that's getting in the way?

Do you have some kind of caching going on at the Apache level for  
files of those extensions?


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Commit problems with certain file types using https:// URLs

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jul 8, 2008, at 04:36, depuys wrote:

> depuys wrote:
>>
>
>> I'm attempting to configure Subversion so all user access is via  
>> Apache
>> and https:// URLs.  Converting CVS repositories and creating new  
>> ones has
>> gone well.  However, the problem we're having is committing  
>> certain file
>> types.  Extensions txt, png, gif, and jpg are problematic.   
>> Extensions
>> cfg, sas, bin, html, java, xml, asdf, c, asc, and tiff are fine.  The
>> errors look like this.
>>
>> svn: Commit failed (details follow):
>> svn: CHECKOUT of
>> '/svn/seerdms/!svn/ver/34186/seerdms/trunk/conf/cp/test_file.txt':  
>> 501
>> Method Not Implemented (https://intranet2.imsweb.com)
>>
>> Transmitting file data ....svn: Commit failed (details follow):
>> svn: PUT of
>> '/svn/bsi/!svn/wrk/0f708b16-414b-11dd-8177-cd479e07ddbe/bsiweb/ 
>> trunk/static/images/kryo_back.png':
>> 405 Method Not Allowed (https://intranet2.imsweb.com)
>>
>> Everything works fine using file:// access.  The Apache error logs  
>> don't
>> report any problems.  The return codes 405 and 501 can be seen in the
>> Apache access logs but nothing helpful is there.  I've looked at the
>> Apache mime types and can't find a correlation between these  
>> types.  I've
>> also looked at ~/.subverison/config and can't gain any insight  
>> into the
>> issue.
>
> I forgot to mention another point I found interesting...  Viewing the
> repository with a Web browser works fine for the files which aren't
> problematic.  The problematic files return a 404 error code to the  
> browser.
> However, if you put a trailing slash on the URL in the broswer's  
> address
> box, the file is displayed correctly.  In other words, a URL ending in
> test_file.txt/ works but without the trailing slash, a 404 is  
> returned.

That's obviously not normal, so something in the way your apache is  
set up must be causing this. Examine your apache configuration file  
and any ancillary configuration files it may be including.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Commit problems with certain file types using https:// URLs

Posted by depuys <de...@imsweb.com>.
I forgot to mention another point I found interesting...  Viewing the
repository with a Web browser works fine for the files which aren't
problematic.  The problematic files return a 404 error code to the browser. 
However, if you put a trailing slash on the URL in the broswer's address
box, the file is displayed correctly.  In other words, a URL ending in
test_file.txt/ works but without the trailing slash, a 404 is returned.


depuys wrote:
> 
> Hello,
> 
> I'm attempting to configure Subversion so all user access is via Apache
> and https:// URLs.  Converting CVS repositories and creating new ones has
> gone well.  However, the problem we're having is committing certain file
> types.  Extensions txt, png, gif, and jpg are problematic.  Extensions
> cfg, sas, bin, html, java, xml, asdf, c, asc, and tiff are fine.  The
> errors look like this.
> 
> svn: Commit failed (details follow):
> svn: CHECKOUT of
> '/svn/seerdms/!svn/ver/34186/seerdms/trunk/conf/cp/test_file.txt': 501
> Method Not Implemented (https://intranet2.imsweb.com)
> 
> Transmitting file data ....svn: Commit failed (details follow):
> svn: PUT of
> '/svn/bsi/!svn/wrk/0f708b16-414b-11dd-8177-cd479e07ddbe/bsiweb/trunk/static/images/kryo_back.png':
> 405 Method Not Allowed (https://intranet2.imsweb.com)
> 
> Everything works fine using file:// access.  The Apache error logs don't
> report any problems.  The return codes 405 and 501 can be seen in the
> Apache access logs but nothing helpful is there.  I've looked at the
> Apache mime types and can't find a correlation between these types.  I've
> also looked at ~/.subverison/config and can't gain any insight into the
> issue.
> 
> Thanks,
> Scott
> 
> 

-- 
View this message in context: http://www.nabble.com/Commit-problems-with-certain-file-types-using-https%3A---URLs-tp18324214p18335382.html
Sent from the Subversion Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Commit problems with certain file types using https:// URLs

Posted by depuys <de...@imsweb.com>.
Found our problem with Apache that caused this...  We're using our company's
Intranet to host Subversion.  In the document root, we had an .htaccess file
with rewrite rules that contained special handling for files with certain
extensions.  No surprise, these were the file types which we couldn't commit
to Subversion.


depuys wrote:
> 
> Hello,
> 
> I'm attempting to configure Subversion so all user access is via Apache
> and https:// URLs.  Converting CVS repositories and creating new ones has
> gone well.  However, the problem we're having is committing certain file
> types.  Extensions txt, png, gif, and jpg are problematic.  Extensions
> cfg, sas, bin, html, java, xml, asdf, c, asc, and tiff are fine.  The
> errors look like this.
> 
> svn: Commit failed (details follow):
> svn: CHECKOUT of
> '/svn/seerdms/!svn/ver/34186/seerdms/trunk/conf/cp/test_file.txt': 501
> Method Not Implemented (https://intranet2.imsweb.com)
> 
> Transmitting file data ....svn: Commit failed (details follow):
> svn: PUT of
> '/svn/bsi/!svn/wrk/0f708b16-414b-11dd-8177-cd479e07ddbe/bsiweb/trunk/static/images/kryo_back.png':
> 405 Method Not Allowed (https://intranet2.imsweb.com)
> 
> Everything works fine using file:// access.  The Apache error logs don't
> report any problems.  The return codes 405 and 501 can be seen in the
> Apache access logs but nothing helpful is there.  I've looked at the
> Apache mime types and can't find a correlation between these types.  I've
> also looked at ~/.subverison/config and can't gain any insight into the
> issue.
> 
> Thanks,
> Scott
> 
> 

-- 
View this message in context: http://www.nabble.com/Commit-problems-with-certain-file-types-using-https%3A---URLs-tp18324214p18615218.html
Sent from the Subversion Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org