100 Continue
The requestor should continue with the request. The server returns this code to indicate that it has received the first part of a request and is waiting for the rest.
101 Switching Protocols
This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so
102 Processing
As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.
200 OK
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
201 Created
The request has been fulfilled and resulted in a new resource being created.
202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
203 Non-Authoritative Information (since HTTP/1.1)
The server successfully processed the request, but is returning information that may be from another source.
204 No Content
The server successfully processed the request, but is not returning any content.
205 Reset Content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
206 Partial Content
The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
207 Multi-Status (WebDAV) (RFC 2518 )
The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
300 Multiple Choices
Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.
301 Moved Permanently
This and all future requests should be directed to the given URI.
302 Found
This is the most popular redirect code, but also an example of industrial practice contradicting the standard. HTTP/1.0 specification (RFC 1945 ) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviors. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
303 See Other (since HTTP/1.1)
The response to the request can be found under another URI using a GET method. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
304 Not Modified
Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified
Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.
305 Use Proxy
The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.
306 Switch Proxy
No longer used.
307 Temporary Redirect (since HTTP/1.1)
In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.
400 Bad Request
The request contains bad syntax or cannot be fulfilled. The server didn't understand the syntax of the request.
401 Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. The request requires authentication. The server might return this response for a page behind a login.
402 Payment Required
The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code has never been used.
403 Forbidden
The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
404 Not Found
The server can't find the requested page. For instance, the server often returns this code if the request is for a page that doesn't exist on the server. The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible. No indication is given of whether the condition is temporary or permanent.
405 Method Not Allowed
A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
406 Not Acceptable
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
407 Proxy Authentication Required
This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field containing a challenge applicable to the proxy for the requested resource.
408 Request Timeout
The server timed out waiting for the request.
409 Conflict
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
410 Gone
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed; however, it is not necessary to return this code and a 404 Not Found can be issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes.
411 Length Required
The request did not specify the length of its content, which is required by the requested resource.
412 Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.
413 Request Entity Too Large
The request is larger than the server is willing or able to process.
414 Request URI Too Long
The URI provided was too long for the server to process.
415 Unsupported Media Type
The request did not specify any media types that the server or resource supports. For example the client specified that an image resource should be served as image/svg+xml, but the server cannot find a matching version of the image.
416 Requested Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion (for example, if the client asked for a part of the file that lies beyond the end of the file).
417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418 I'm a teapot
The HTCPCP server is a teapot. The responding entity MAY be short and stout. This code was defined as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.
422 Unprocessable Entity (WebDAV) (RFC 4918 )
The request was well-formed but was unable to be followed due to semantic errors.
423 Locked (WebDAV) (RFC 4918 )
The resource that is being accessed is locked
424 Failed Dependency (WebDAV) (RFC 4918 )
The request failed due to failure of a previous request (e.g. a PROPPATCH).
425 Unordered Collection (RFC 3648 )
Defined in drafts of WebDav Advanced Collections, but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".
426 Upgrade Required (RFC 2817 )
The client should switch to TLS/1.0.
449 Retry With
A 微软 extension. The request should be retried after doing the appropriate action.
450 Blocked by Windows Parental Controls
A 微软 extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.
500 Internal Server Error
A generic error message, given when no more specific message is suitable.
501 Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the downstream server.
503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely request from the downstream server.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 Variant Also Negotiates (RFC 2295 )
Transparent content negotiation for the request, results in a circular reference.
507 Insufficient Storage (WebDAV) (RFC 4918 )
509 Bandwidth Limit Exceeded (Apache bw/limited extension)
This status code, while used by many servers, is not specified in any RFCs.
510 Not Extended (RFC 2774 )
Further extensions to the request are required for the server to fulfill it.
XML 地图 | Sitemap 地图
机筒螺杆标准配件_js金沙登入网址118
舟山js金沙登入网址118机械js金沙登入网址118

锐意进取、创新致远

  • 专业设计、制造螺杆、机筒、料筒的生产企业
  • 全国咨询电话  0580-8592012

    二维码

    扫一扫 查看更多信息:

     

    二维码
  • 产品名称:机筒螺杆标准配件
  • 注塑机螺杆配件

    注塑机螺杆的材质分类:

    1、HPT全硬化粉末合金螺杆采用采用钨钴粉末合金工具钢,经特殊工艺整体硬化处理成型,螺杆内部与外部整体硬度相同, 达到HRC65°左右。适合加工各种透明产品、精密产品以及添加纤维LCP.,PPS.PES.PPA,磁粉,电木等特殊性高温高腐蚀性塑料。

    2、双合金螺杆采用SACM645、38CrMoAlA为基材,然后牙顶或者螺槽离子喷焊碳化钨镍基合金,皮膜密度为98~99.9%,密度强度:10000psi以上,合金层厚度0.8—2.5mm,螺杆表面硬度在HRC60°左右。

    3、电镀螺杆采用SACM645、38CrMoAlA为基材,成型过后外表面电镀一层硬铬、镍、钛等元素。镀层厚度为0.03—0.06mm,硬度在HRC60°左右。

    4、不锈钢螺杆材质为9Cr18MoV特殊不锈工具钢,采用整体淬火+整体硬化处理,整体硬度在HRC55°左右

    5、普通氮化螺杆采用SACM645、38CrMoAlA为基材经特殊工艺处理成型,氮化层深度0.5mm—0.8mm,整体硬度HV980~1080°适合加工普通塑料。

    6、螺杆经特殊工艺处理成型,产品韧性好,抗扭力强。

    总结优势:注塑机螺杆采用HPT全硬化粉末合金经特殊工艺处理成型,该产品具有耐磨损,耐腐蚀,耐高温高压的特点,适合注塑精密产品和添加玻纤的工程产品。

    注塑机筒

    产品先容:

    机筒在挤出压塑系统中和一样,是挤出机的重要零件。机筒与螺杆配合工作,机筒包容螺杆,螺杆在机筒内转动。

    机筒与螺杆的正常配合工作,保证了挤出机的连续挤塑原料成型生产。

    产品结构:

    机筒的结构比较简单。

    在大型挤出机中,机筒的结构可由几段组成。

    由于机筒分为几段组成,则每段机筒的长度缩小了,这给机械加工机筒带来了方便。

    但是,这种由几段组成的机筒,机械加工后的内径尺寸和几段机筒的内孔同心度精度比较难达到一致;

    此外,分段机筒用法兰连接,给机筒的加热和冷却设备布置也会带来些难度,温度控制也不会太均匀。

    为了节省较贵重的合金钢材,有些大型挤出机的机筒采用内孔加衬套或浇铸耐磨合金层的方法。

    这样的机筒外套体可由普通钢铸造,达到降低机筒的制造费用的目的。

    热销产品推荐

    XML 地图 | Sitemap 地图